Satellite system using cloud computing virtualized gateways, radio transport protocol and on-ground beamforming

ABSTRACT

A satellite system uses cloud computing virtualized gateways, radio transport protocol and on-ground beamforming to improve wireless communication. A digitized ground based subsystem for use with the satellite system can be employed in transmitting an optical feeder uplink beam to a communications platform that includes a multiple element antenna array. The ground based subsystem is configured to receive the optical feeder uplink beam and, in dependence thereon, use the multiple element antenna feed array to produce and transmit a plurality of RF service downlink beams to a single or plurality of service terminals.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation patent application which claimspriority under 35 U.S.C. § 120 to U.S. Ser. No. 17/303,939, filed Jun.10, 2021, and under 35 U.S.C. § 119 to provisional patent applicationU.S. Ser. No. 63/037,955, filed Jun. 11, 2020. These applications areherein incorporated by reference in their entireties, including withoutlimitation, the specification, claims, and abstract, as well as anyfigures, tables, appendices, or drawings thereof.

FIELD OF THE INVENTION

The present invention relates generally to an apparatus and/orcorresponding method of use in at least the communications, aerospace,and cloud computing industries. More particularly, but not exclusively,the present invention relates to a satellite system using cloudcomputing virtualized gateways, radio transport protocol and on-groundbeamforming.

BACKGROUND OF THE INVENTION

The background description provided herein gives context for the presentdisclosure. Work of the presently named inventors, as well as aspects ofthe description that may not otherwise qualify as prior art at the timeof filing, are neither expressly nor impliedly admitted as prior art.

As the need for high bandwidth satellite communications continuouslyincreases so does the need for greater flexibility in delivering thecommunications services in the manner that best suites the applicationssupported and associated customer requirements.

Satellite communications architectures suffer from several problems withtheir implementations and critically from an inflexibility that leads tothe inability to maximize the efficiency of the end-to-end satellitecommunication resource. With current architectures it is extremelydifficult to contract one-hundred percent (100%) of the available radiofrequency (RF) spectrum and/or power on a satellite with the customerbase (especially with HTS, VHTS and UHTS), but crucially these systemsprohibit achieving anywhere near high levels of satellite communicationsresource utilization as multiple segments of all sizes can lie dormantfor frequent and/or extensive periods while the end customers no longeruse the assets. This represent two fundamental issues, firstly thecustomer pays for an asset that they neither utilize completely or fullyneed, and secondly there are no effective solutions or technologies tosignificantly increase the overall satellite communications resourceutilization across a varied and varying customer base. This situationfurther suffers when specific customers wish the ability to modify theircontracted satellite communications resources in a dynamic, scheduledand/or ad-hoc sporadic manner, to no avail.

This problem is further exacerbated by the fact that satellitecommunications cover huge geographic areas, which means that its‘last-mile’ segment (satellite-subscriber terminal) can capture hugecustomer numbers, segments and/or applications, representing a huge,stymied demand. This stymied demand is represented by different customersegments with differing applications of varying network configurations,beam laydowns and coverage, demand schedules, satellite baseband airinterface types, and/or associated remote end subscriber terminalsupport. Current technology suffers from the inability to flexiblymanage and operate effectively and efficiently across a customer baserepresenting unique segments requiring network bandwidth in differentplaces, in different times, and/or in differing formats.

Such inflexibility is caused by current architectural issues in both theground and space segment components.

Current gateway architectures are highly dependent on vastimplementations of multiple bespoke, vendor proprietary dedicatedhardware infrastructure. Many of which are non-interoperable and all ofwhich operate significant portions within the hardware analog RF domainto transmit signals internally and externally of the gateway. This leadsto a highly fractalized or stove-piped infrastructure that iscumbersome, inflexible, and exceedingly difficult to operate, maintain,upgrade, augment and/or reconfigure at short notice and/or in a dynamicmanner.

Current architectures utilize gateway-satellite links that are operatedin the analog RF domain, one of the few communications infrastructuresleft that operates the middle-mile (gateway-satellite) in a restrictiveanalog domain.

The analog RF domain is an extensive and inherently hard-codedenvironment to operate within and satellite communications suffers fromrestricting the analog RF domain solely to the last-mile(satellite-subscriber terminal).

The RF gateway-satellite feeder link architectures require manyconcurrent geographically dispersed gateways to support high throughputsatellites (HTS), very high throughput satellites (VHTS) and ultra highthroughput satellites (UHTS). Even the availability of 5 GHz at V band,and dual polarization, a satellite with terabit/second (Tbps) capacitywould need between forty (40) and seventy (70) gateways depending onspectral efficiency achieved, as described in the conference papertitled “Optical Feeder Links for VHTS—System Perspectives”, byMata-Calvo et al. (Conference Proceedings of the Ka Band Communications,Navigation and Earth Observation Conference 2015. Ka Conference 2015,12-14 Oct. 2015, Bologna Italy). Note that Q/V band and Ka band gatewaystypically require additional resiliency and redundancy implementationsto achieve high availability.

Satellite communications offer large swath views of the Earth's surfaceprovides an ideal platform for beamforming and the laydown of capacity.Emerging and developing high-throughput satellite communicationsbeamforming technologies are focusing on complex, physically limited andhighly expensive satellite onboard processing hardware where thebeamforming computational burden is placed on the satellite andhard-coded for the duration of the mission, which can run anywhere up tofifteen to twenty (15-20) years or higher. This limits the investment ina satellite as the hardware specification and capabilities are lockedtypically at least 2 year prior to launch and will be obsolete evenprior to reaching orbit, let alone 15-20 years later. Such hardwaredependent systems suffer from being fixed implementations and thusnon-upgradeable after launch. They are highly dependent on the hardwarecapabilities coded and locked in at the level of technology available atbest two (2) years prior to launch.

Such onboard satellite communications beamforming systems rely on thehard-coded gateway implementations, gateway hardware RF stove piping,analog RF gateway to satellite feeder links, and/or extensive andcomplex RF componentry onboard the satellite. Further, the onboardsatellite communication beamforming systems do not support the complexissues of integration with the higher layers (OSI Layer 2 and above) ofmultiple and/or dynamic satellite baseband air interface operations oftoday let alone those of the future.

The satellite communications industry has developed a multi-vendorecosystem through multiple satellite operators, service providers and/orsatellite baseband air interface systems. Although this open-systemapproach enables multi-application and multi-vendor markets thatdelivers innovation and competition, it suffers from the hard-codedecosystems that restrict the ability to holistically view, utilize,adapt, and maximize the return on available satellite communicationsresource such as RF spectrum, power, human resource, space and/or groundinvestments. Additionally, current technology does not allowimplementations that deliver the ability to holistically view, utilize,adapt, coordinate, and maximize the return on available satellitecommunications resource across multiple satellites owned and operated bya single and/or multiple satellite operators.

U.S. Pat. No. 10,142,021 proposes a solution to some of the multiple RFgateway and onboard processing issues by utilizing an optical feederlink between the gateway and satellite and placing the beamformingburden on the ground with a ground based beamforming system (GBBF).However, it suffers from multiple limitations and problems, such as:

-   -   expanding the rigid, inflexible, costly, and cumbersome        hard-coded and stove-piped gateway environment and        implementations;    -   operation in the analog domain within the middle-mile;    -   requiring extensive and inflexible hard-coded GBBF hardware and        gateway analog RF to optical conversion hardware;    -   requiring the utilization of much higher power demanding analog        RF modulated optical terminal system (gateway and satellite);    -   requiring complex, extensive and highly lossy analog RF chains        on board the satellite;    -   providing no effective operational system to manage multiple        optical gateways to provide high availability. Even though        optical feeder links provide vastly greater capacity when        compared to RF variants even in V band, there is still a need to        compensate link blockage by clouds through optical feeder link        diversity. By analysis of long-term cloud data, it can be shown        that in the Mediterranean, around eleven (11) gateway stations        can be sufficient to fulfill availability requirements for        satellite communications systems, while this number can even be        reduced when an inter-hemispherical ground network exploiting        anti-correlated seasonal weather statistics, as described in the        paper titled “Preliminary Results of Terabit-per-second        Long-Range Free-Space Optical Transmission Experiment THRUST”,        by Giggenbach et al. (Proc. of SPIE 9647-21, 2015). Resiliency        and redundancy suffer heavily when multiple hardware gateways        must be exactly matched with hard-coded stove-piped        configurations resulting in costly implementations that are        impossible to modify in a real-time environment and entail        complex coordination for any required systems upgrades;    -   offers no solution to support beamforming integration with        dynamic and/or multi satellite baseband air interface operation;        and    -   operation only with an extensive hardware dependent fractalized        gateway infrastructure including hard-coded satellite baseband        air interface systems.

Several ground to space Terabit per second (Tbps) optical feeder linktechnologies that operate within the digital domain are currently inprocess, however these technologies only provide a baseband link fromthe gateway to the satellite (e.g., raw Internet Protocol (IP) user databetween the gateway and the satellite). As such, they suffer frommultiple limitations and problems, such as:

-   -   onboard processing cost, obsolescence, and capability        limitations;    -   requiring extensive and multiple onboard modulation and        demodulation technologies to convert RF to/from baseband;    -   no comprehensive integration of onboard satellite baseband air        interface, or multiple and/or dynamic satellite baseband air        interface support;    -   lack of onboard scalability and flexibility in matching        satellite baseband air interface functions with beamforming        functions;    -   no holistic, comprehensive and/or effective management of        end-to-end satellite communications resource such as RF        spectrum, power, space and/or ground investments; and    -   inability to holistically view, utilize, adapt, coordinate, and        maximize the return on available satellite communications        resource either across the satellite or multiple satellites        owned and operated by a single and/or multiple satellite        operators.

Thus, there exists a need in the art for satellite communicationsservices that can be delivered via a highly flexible, scalable, dynamic,interchangeable, and easily adaptable end-to-end architecture.

SUMMARY OF THE INVENTION

The following objects, features, advantages, aspects, and/orembodiments, are not exhaustive and do not limit the overall disclosure.No single embodiment need provide each and every object, feature, oradvantage. Any of the objects, features, advantages, aspects, and/orembodiments disclosed herein can be integrated with one another, eitherin full or in part.

It is a primary object, feature, and/or advantage of the presentinvention to improve on or overcome the deficiencies in the art.

It is a further object, feature, and/or advantage of the presentinvention to simultaneously accommodate and satisfy the multiple demandsof multiple applications and multiple customer types in a dynamicenvironment.

It is still yet a further object, feature, and/or advantage of thepresent invention to deliver effective interoperability of groundsystems and space segment in highly dynamic, volatile, uncertain,complex and/or disruptive environments.

It is still yet a further object, feature, and/or advantage of thepresent invention to quickly, easily and/or automatically adapt andmorph to meet real-time changing demands.

It is still yet a further object, feature, and/or advantage of thepresent invention to enable the visibility, operation, management andreporting of the entire satellite communications resource holisticallyacross a single satellite and/or multiple satellites under a single ormultiple of satellite owner operators.

It is still yet a further object, feature, and/or advantage of thepresent invention to improve inter-coordination performance betweensatellites.

It is still yet a further object, feature, and/or advantage of thepresent invention to decrease product development cycles and cost.

It is still yet a further object, feature, and/or advantage of thepresent invention to enable feature augmentation and performanceimprovements in a software virtual environment without major and/orfrequent hardware upgrades and capital investment.

It is still yet a further object, feature, and/or advantage of thepresent invention to provide a platform to add new features andcapabilities incrementally and frequently within an agile DevOps orDevSecOps environment.

It is still yet a further object, feature, and/or advantage of thepresent invention to provide a solid software defined test anddevelopment environment that allows quick and easy transition to thebeta and operational phases smoothly and quickly with minimal impact toexisting operational services.

It is still yet a further object, feature, and/or advantage of thepresent invention to provide an effective interface for advanced controland monitoring such as artificial intelligence and or machine learningalgorithms. The advanced control and monitoring should minimize theobsolescence and maximize the futureproofing of both the space hardwareand ground segment investment.

It is still yet a further object, feature, and/or advantage of thepresent invention to provide a higher level of flexibility in satellite(platform) user beam laydown options and performance.

It is still yet a further object, feature, and/or advantage of thepresent invention to be able to reconfigure a completely virtual gatewayinfrastructure near instantaneously.

It is still yet a further object, feature, and/or advantage of thepresent invention to negates the traditional approach of extensive,complex, bespoke and cumbersome gateway radio frequency hardwareequipment stove-piping.

It is still yet a further object, feature, and/or advantage of thepresent invention to simplify gateway development.

It is still yet a further object, feature, and/or advantage of thepresent invention to improve functionality by providing an ability toaugment third party value-add services.

It is still yet a further object, feature, and/or advantage of thepresent invention to offer more total configuration options in networkdesign, a higher performance capacity, and a larger number ofperformance capability options than those satellite systems known in theart.

It is preferred the apparatus be safe, cost effective, and durable. Forexample, satellite systems disclosed herein have a lower cost gatewayinvestment and operating costs than those known in the art. Ideally,these satellite communication systems maximize total satellitecommunications resource efficiency and return on investment and toreduces capital and operational expenditures, simplify and standardizethe satellite architecture and hardware capable of delivering highlyunique services, are provided within an ecosystem that enables asatellite communications cloud marketplace to drive innovation, lowercost, maximize performance and enhance services. According to a morespecific non-limiting aspect, the satellite system can include a highergateway resiliency.

Methods can be practiced which facilitate use, manufacture, assembly,maintenance, and repair of satellite systems which accomplish some orall of the previously stated objectives. For example, there can exist anability to easily upgrade features and performance in a softwareenvironment, and to allow for changes significantly and frequently withlittle to no physical hands-on tasking that is ideally suited to operateflawlessly under pandemic and/or social distancing situations. In yetanother example, a higher level of oversight and management withholistic view of total resource is provided.

The satellite systems and their components disclosed herein can beincorporated into other systems which accomplish some or all of thepreviously stated objectives.

According to some aspects of the present disclosure, a method ofwirelessly communicating using cloud computing virtualized gateways,radio transport protocol, and on-ground beamforming comprises:communicatively coupling at least one cloud computing gateway ecosystem(CCGE) to a plurality of subscriber terminals; illuminating specificregions of the Earth's surface with user spot beams containing thesubscriber terminals, wherein each user spot beam includes a downlinkchannel and an uplink channel; allowing two-way communication betweenthe CCGE and the communications platform over a feeder link within thefield of view of the communications platform, wherein the feeder linkincludes a forward link and a return link; creating data signals for theforward link based upon data received from external networks underparameters controlled by a network management system (NMS); outputtingthe forward link user data signals to a controller configured to packagethe data signals together and map the forward link user data signals toan associated user spot beam; creating digitized RF carrier waves in aparticular RF based upon the associated user spot beam; digitallymodulating and mapping bit streams that are beamformed and transportedwithin data packets (DP) and associated metadata packets (MP) to aground optical communication feeder link system (GOCFLS) co-located orgeographically distanced from the CCGE; forwarding the return link tothe CCGE; and monitoring and controlling a feeder link resiliency systemthat allows for switching of CCGEs and associated GOCFLSs to ensureoperator specified availability of the feeder link system to thecommunications platform.

According to some additional aspects of the present disclosure, thesubscriber terminal is selected from the group consisting of: a wirelessmodem, a cellular telephone, a wireless handset, a data transceiver, apaging or positioning determination receiver, or mobile radio-telephone,and a head end of a local network.

According to some additional aspects of the present disclosure, thecommunications platform includes a plurality of sub-systems selectedfrom the group consisting of: a power source, solar panels, a propulsionsystem, a momentum control system, and an attitude control system.

According to some additional aspects of the present disclosure, theplurality of subsystems utilize core cloud computing resources that areprovided at a cloud-computing data center (CDC) comprising one or morecomponents selected form the group consisting of: a computer, a server,a database, a network, an analytics based software application, acontrol system, intelligence capabilities, and on-demand web-basedservices.

According to some additional aspects of the present disclosure, thenetwork is selected from the group consisting of: the Internet, a widearea network (WAN), a public switch telephone network, a mobiletelephone network, a private server, and an intranet network.

According to some additional aspects of the present disclosure, themethod further comprises delivering the CCGE via a private cloudon-premises solution where the software is installed locally or on apublic/private hybrid cloud combination.

According to some additional aspects of the present disclosure, themethod further comprises selecting an Infrastructure-as-a-Service(IaaS), a Platform-as-a-Service (PaaS), and/or Software-as-a-Serviceofferings (SaaS) offering to operate the communications platform onbased upon a nature and/or requirements of the communications platform.

According to some additional aspects of the present disclosure, themethod further comprises sensing, monitoring, and/or controllingenvironmental aspects of the communications platform; and managingand/or coordinating at least a partial amount of resources of thecommunications platform based upon the sensed, monitored, and/orcontrolled environmental aspects.

According to some additional aspects of the present disclosure, themethod further comprises storing software images, run-time data andother non-RAM functional data.

According to some other aspects of the present disclosure, a digitizedground based subsystem for use in transmitting an optical feeder uplinkbeam to a communications platform comprises an antenna array configuredto receive the optical feeder uplink beam and to use the multipleelement antenna feed array to produce and transmit a plurality of RFservice downlink beams to a service terminal; a cloud-computing datacenter (CDC); a virtualized air interface system configured to accept aplurality of data streams, multiplex the data streams, and produce aplurality of user data signals; a virtualized user data signal-spot beamcontroller (VUDSSBC) configured to accept the user data signals from thevirtualized air interface systems and combine subsets of the user datasignals into a plurality of user spot beam signals; a virtualizeddigital modulator and mapper configured to accept the user spot beamsignals from the VUDSSBC and convert each to a digitized RF user spotbeam signal; a virtualized on-ground beamformer (VOGB) configured toaccept the digitized RF user spot beam signals from the virtualizeddigital modulator and mapper, produce or otherwise obtain phase andamplitude coefficients, and output a plurality of digitized RF transmitantenna element signals in dependance of the plurality of the digitizedRF user spot beam signals and phase and amplitude beamformingcoefficients; a virtualized packet based radio transport (VPBRT)configured to accept the digitized RF transmit antenna element signalsfrom the VOGB and packetizes in a plurality of information streams formultiplexing and transmission over a digital packet switched network;and a ground optical communications feeder link system (GOCFLS)configured to accept the digitized RF transmit antenna element signalsin packetized form from the VPBRT and transmit the RF transmit antennaelement signals to the communications platform.

According to some additional aspects of the present disclosure, thesubsystem further comprises a cloud computing gateway management andinterface system (CCGMIS) configured to monitor the GOCFLSs performanceand dynamically orchestrate the ground base subsystem, and the switchingoperations of the ground base subsystem between different CDCs andGOCFLSs supporting the communications platforms.

According to some additional aspects of the present disclosure, thesubsystem further comprises a CCGMIS configured to orchestrate ascheduled and/or dynamic operation of a plurality of virtualized airinterface systems between active, dormant and/or modified states.

According to some additional aspects of the present disclosure, thesubsystem further comprises a CCGMIS configured with a plurality ofcommunications platforms' inter-coordination agreement parameters tomonitor and control the user spot beam RF frequency and powercoordination across the plurality of the communications platforms.

According to some other aspects of the present disclosure, a system fora space based satellite comprises a ground optical communications feederlink system (GOCFLS) configured to accept digitized RF transmit antennaelement signals in packetized form and to transmit the RF transmitantenna element signals to a communications platform; a cloud-computingdata center (CDC); a satellite bus system; a space optical communicationfeeder link system (SOCFLS) configured to accept the digitized RFtransmit antenna element signals in packetized form from the GOCFLS; anon-board digital network distribution system (OBDNDS) configured toaccept the digitized RF transmit antenna element signals from the SOCFLSand perform packet based switched networking functions aboard thesatellite; an on-board processor: packet based radio transport (OBPPBRT)configured to accept the digitized RF transmit antenna element signalsin packetized form from the OBDNDS that de-multiplexes and de-packetizesthe information streams; a plurality of on-board processor:digital-to-analog converters (OBPDAC) configured to accept thede-packetized digitized RF transmit antenna element signals from theOBPPBRT, and converting to a plurality of analog RF transmit antennaelement signals; a transmit RF distribution system (TRFDS) configured toaccept the analog RF transmit antenna element signals from the OBPDAC,and distribute through a plurality of analog RF chains; and a pluralityof transmit antenna elements configured to accept a single analog RFtransmit antenna element signal from the TRFDS to produce and transmit aplurality of RF service downlink beams to the service terminals.

According to some additional aspects of the present disclosure, thesubsystem further comprises a cloud computing gateway management andinterface system (CCGMIS) configured to monitor the GOCFLS's performanceand dynamically orchestrate the ground base subsystem, and the switchingoperations of the ground base subsystem between different CDCs andGOCFLSs supporting a satellite.

According to some additional aspects of the present disclosure, theCCGMIS is configured to orchestrate a scheduled and/or dynamic operationof a plurality of virtualized space link air interface system (VSLAIS)between active, dormant and/or modified states.

According to some additional aspects of the present disclosure, theCCGMIS is configured with a plurality of satellites' inter-coordinationagreement parameters to monitor and control the user spot beam RFfrequency and power coordination across the plurality of the satellites.

According to some additional aspects of the present disclosure, thesubsystem further comprises an OBPDAC configured to support operationacross multiple RF spectrum bands; a TRFDS configured to supportoperation across multiple RF spectrum bands; a plurality of transmitantenna elements configured to support operation across multiple RFspectrum bands; and an antenna configured to support operation acrossmultiple RF spectrum bands.

According to some additional aspects of the present disclosure, thesubsystem further comprises a CCGMIS configured to orchestrate ascheduled and/or dynamic operation of a plurality of VSLAISs of variousRF spectrum bands between active, dormant and/or modified states.

These and/or other objects, features, advantages, aspects, and/orembodiments will become apparent to those skilled in the art afterreviewing the following brief and detailed descriptions of the drawings.Furthermore, the present disclosure encompasses aspects and/orembodiments not expressly disclosed but which can be understood from areading of the present disclosure, including at least: (a) combinationsof disclosed aspects and/or embodiments and/or (b) reasonablemodifications not shown or described.

BRIEF DESCRIPTION OF THE DRAWINGS

Several embodiments in which the present invention can be practiced areillustrated and described in detail, wherein like reference charactersrepresent like components throughout the several views. The drawings arepresented for exemplary purposes and may not be to scale unlessotherwise indicated.

FIG. 1 shows a diagrammatic view of a wireless communication system,according to some aspects of the present disclosure.

FIG. 2 shows a diagrammatic view depicting ground systems and equipment,according to some aspects of the present disclosure.

FIG. 3 shows a diagrammatic view depicting the space segment systems andequipment, according to some aspects of the present disclosure.

FIG. 4 shows a diagrammatic view describing a gateway switching system,according to some aspects of the present disclosure.

FIG. 5 shows a diagrammatic view describing the dynamic multi airinterface operation, according to some aspects of the presentdisclosure.

An artisan of ordinary skill in the art need not view, within isolatedfigure(s), the near infinite number of distinct permutations of featuresdescribed in the following detailed description to facilitate anunderstanding of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present disclosure is not to be limited to that described herein.Mechanical, electrical, chemical, procedural, and/or other changes canbe made without departing from the spirit and scope of the presentinvention. No features shown or described are essential to permit basicoperation of the present invention unless otherwise indicated.

Ground Segment/High-Level

FIG. 1 depicts a high-level block diagram of a wireless communicationsystem that includes a communications platform 100. The communicationsplatform 100 can be a space based satellite located, for example, at ageostationary or non-geostationary orbital location. In otherembodiments, other platforms may be used in addition to or in lieu ofcommunications platform 100, such as: a manned aerial vehicle, anunmanned aerial vehicle (UAV), a free floating balloon, and/or atethered balloon.

Platform 100 may be communicatively coupled to at least one cloudcomputing gateway ecosystem (CCGE) 101, and a plurality of subscriberterminals (ST) (including subscriber terminals 102, 108, and 109). Asused herein, even if the plural term “subscriber terminals” is used, oneof ordinary skill in the art will appreciate there will be someapplications where the use of only one subscriber terminal will suffice.Moreover, although FIG. 1 only shows two (2) subscriber terminals 102,108, and 109 within each region, a typical system may have thousands ormore of subscriber terminals within each region. A subscriber terminals102, 108, 109 can support a single or plurality of users.

According to a non-limiting example, the subscriber terminals 102, 108,and 109 can be adapted for communications with the wirelesscommunication platform 100 and/or may be satellite(s).

The subscriber terminals 102, 108, 109 may include fixed and mobileterminals including, but not limited to, a wireless modem, a cellulartelephone, a wireless handset, a data transceiver, a paging orpositioning determination receiver, or mobile radio-telephone, or a headend of a local network. According to some non-limiting aspects of thepresent disclosure, the subscriber terminal can be handheld or largercustomer premise equipment, portable (including vehicle mountedinstallations for aircraft, trucks, boats and maritime vessels, trains,etc.), and/or fixed as desired.

Where the communication platform of a wireless communication system is aspace based satellite, the wireless communication system can refer tomore specifically as the satellite communication system. For theremainder of this description, unless it is stated otherwise, it isassumed that the communication platform 100 is the satellite.Accordingly, platform 100 will be referred to as a satellite 100.

In some embodiments, satellite 100 comprises a spacecraft bus and one ormore payloads (e.g., the communication payload). The satellite 100includes multiple sub-systems, such as but not limited to, multiplepower sources, batteries, solar panels, and one or more propulsionsystems, momentum control systems, attitude control systems foroperating the bus and the payload. In other embodiments, other bussystems components and configurations can be utilized.

At least one CCGE 101 may be coupled to a network or multiple networks103 such as for example the Internet, public switch telephone network,mobile telephone network, or a private server or intranet network, etc.

The CCGE 101 and the satellite (or platform) communicate over a feederlink, which has both an uplink 104 u and a downlink 104 d. In someembodiments, the feeder link covers the Earth's surface (or anothersurface).

Although a single CCGE 101 is shown, some implementations will includemultiple CCGEs 101.

Subscriber terminals (STs) 102, 108, and 109 and satellite 100communicate over service beams, which are also known as user spot beams.For example, FIG. 1 shows user spot beams 105, 106 and 107, illuminatingspecific regions of the Earth's surface (or another surface). Thecommunication system will include more than three user spot beams (e.g.sixty, one thousand, etc.), and the user spot beam size and coverageconfiguration can vary.

Each user spot beam 105, 106, and 107 has a single or plurality ofdownlink channel(s) 105 d, 106 d and 107 d, and a single or plurality ofuplink channel(s) 105 u, 106 u, 107 u. The uplink and downlink channelscarry user data signals.

In some embodiments, end-to-end communication within the system in FIG.1, follows a nominal two-way direction whereby data is received by CCGE101 from network 103 (e.g., the Internet) and sent to a set ofsubscriber terminals and vice versa. In one example, communication overthe forward link comprises transmitting the data from the CCGE 101 tothe satellite 100 via the uplink feeder link 104 u and from thesatellite 100 to one or more subscriber terminals via the downlink ofone of the user spot beams (e.g., 105 d).

Data can also be sent from the subscriber terminals 102, 108, and 109over the return link to the CCGE 101. In one example, communication overthe return path comprises of transmitting data from the subscriberterminal (e.g., subscriber terminal 102 in service beam 105) tosatellite 100 via uplink 105 u of user spot beam 105, and from satellite100 to CCGE 101 via downlink feeder link 104 d whereby the data is sentby CCGE 101 to a connected network 103 (e.g., the Internet).

Although the above example uses spot beam 105 the example could haveused any user spot beam, such as spot beams 106/107 or another spot beamnot shown.

Ground Segment

FIG. 2 depicts the block diagram of the ground component of thesatellite communication system. The cloud computing gateway ecosystem(CCGE) 200 is a new architecture in the function of a single orplurality of gateways serving a single or plurality of satellites, thusmultiple CCGEs are supported at multiple cloud data centers (CDCs).

The CCGE 200 and its sub-systems utilize core cloud computing resourcesthat are provided at a CDC such as, but not limited to servers, compute,storage, databases, networking, software,configuration/management/control, analytics, and intelligencecapabilities and services.

The means of delivering the CCGE 200 is independent of the underlyingcloud computing resource architecture. It can be delivered via a privatecloud on-premises solution where the software is installed locally onnon-cloud based computers and servers. Additionally, it can be deliveredvia public off-premises solutions hosted by a third-party cloud serviceproviders (CSP) (e.g., Amazon Web Services (AWS), Microsoft Azure,Google Cloud, etc.), or could be delivered by a combination of the twowith a hybrid solution.

The CCGE 200 and its sub-systems can be collocated or geographicallydistributed due to the virtualized nature of its subsystems. In someembodiments, the collocated model will be utilized for simplicity bothin design and operation.

The underlying resources and subsystems of the CCGE 200 can be deliveredthrough the multiple embodiments with options available from cloudcomputing technologies and/or services offered by the cloud computingindustry. Such technologies and services are varied and representsseveral means of carrying-out tasks and solving problems.

Cloud computing provides multiple attributes such as, but not limitedto, efficiency, adaptability, accessibility, scalability, upgradability,flexibility, affordability, resiliency, reliability, and augmentable.Cloud computing additionally provides specific commercial operationalattributes and technologies, such as but not limited to, on-demand andpay-as-you-use, and/or volume based pricing mechanisms.

In some embodiments utilizing a third party CSP, the CCGE 200 can bedesigned to run on an Infrastructure-as-a-Service (IaaS) offering due tothe nature and bespoke requirements of the system. However, it isfeasible that with the fast and ever-changing products/services offeredby the cloud computing industry, that other embodiments couldeffectively run on a mixture of standard or enhancedPlatform-as-a-Service (PaaS) offerings and/or Software-as-a-Serviceofferings (SaaS). The preferred third-party CSP embodiment can bringextensive and additional advantages and value-added services to thewhole satellite communication system within a virtualized ecosystemthrough scale, accessibility, innovation, democratized advancedtechnologies, and cloud marketplaces.

The CCGE 200 provides a virtualized gateway environment which, in someembodiments, can include:

-   -   I. the gateway transport sub-systems of the end-to-end satellite        communication system that permits the efficient and effective        transmission and reception of information to/from subscriber        terminals;    -   II. the enablement of new methods, features and services        (virtualized or traditional) to manage, sense, monitor, control        and/or coordinate the partial/total resources of the single        satellite or plurality of satellites (or fleet of satellites);        and/or    -   III. an effective interface to other virtualized cloud-based        resources, capabilities and value-add products and services        (FIG. 2, 209).

The use of on-demand cloud computing platforms and applicationprogramming interfaces (APIs) (e.g., the Amazon Web Services (AWS)Global Infrastructure) can support the delivery and operation of theCCGE 200, for both a single and multi-vendor virtualized satellitecommunications ecosystem.

The CCGE 200 utilizes a cloud connected digital switched network (CCDSN)210 that enables multiple resources, services, workloads, and virtualmachine (VMs) to communicate with one another internally within the CCGE200 and a connection to any external network or resource, such as butnot limited to, Internet, public switch telephone network, mobiletelephone network, other dispersed cloud resources, or a private serveror intranet network, etc. For example, the use of AWS core networkingservices such as, but not limited to, Amazon Virtual Private Cloud (VPC)can allow separation of core virtualized resources, AWS Transit Gatewaycan enable streamlined and centralized routing of multiple VPCs, AmazonRoute 53 can effectively connect user requests to infrastructure runningin AWS—such as Amazon Elastic Compute Cloud (EC2) instances, elasticload balancers, or Amazon Simple Storage Services (S3) buckets and toroute data to infrastructure and networks outside of AWS, and anyon-premises networks, public and private subnets associated IPaddresses, security groups and firewalls, etc.

In some embodiments, the CCGE 200 and CCDSN 210 utilize the InternetProtocol (IP) to facilitate the packet based digital networkingrequirements. As such the features of IP are available to supportoperations of the end-to-end satellite communication system.

Similar to cloud based systems, the CCDSN 210 is independent of thephysical networking technologies and hardware that support IP functions.

In some embodiments, up to (and including) all components of the CCGE200 and the satellite (FIG. 3, 300) can reside within the same IP subnetand thus negating any Layer 3 routing functionality. In otherembodiments, Layer 3 routing, and other IP functionality are permitted.

Although the primary embodiment details the CCGE 200 connecting to thesatellite (FIG. 3, 300), the CCGE 200 can scale and support a single orplurality of satellites where the sub-systems of the CCGE 200 areduplicated at the same CDC.

A virtualized space link air interface system (VSLAIS) 201 manages thenetwork operations of a single or plurality of communication airinterfaces (or access methods) suitable for air/space link operationsand the conversion of user data information to/from baseband. The VSLAIS201 couples to a single or plurality of networks 202 such as but notlimited to, the Internet, terrestrial public switched telephone network,mobile telephone network or private server networks etc.

FIG. 2 shows a single VSLAIS 201, but more can be supported (e.g., five(5), forty (40), one hundred (100), etc.). Each VSLAIS 201 supports asingle or plurality of transmit (forward link) and receive (return link)user data signals. The user data signal can be of a single or pluralityof proprietary or open standard air interface types, such as but notlimited to, digital video broadcasting satellite (DVB), such asDVB-Second Generation (DVB-S2X), time division multiplexing (TDM),frequency time division multiple access (F-TDMA), single channel percarrier (SCPC), carrier-in-carrier (CNC), and code division multipleaccess (CDMA).

The VSLAIS 201 can support any version of a legacy, current or futuresatellite communications baseband air interface system.

In some embodiments utilizing a legacy and/or current satellitecommunication baseband air interface system, the virtualization processinvolves the porting or migration of some or all of the existing airinterface functions currently delivered on standalone, on-premisesand/or dedicated hardware resources, to the cloud computing resources.

In some embodiments integrating current and/or legacy air satellitecommunication baseband air interface system into the CCGE 200 and cloudcomputing resource, the use of new application programming interface(s)to interface in a purely digitized RF domain is beneficial, as is themigration of other existing software images, programs and/orapplications.

CSPs and cloud technology vendors offer migration capabilities to assistclients port their on-premises software, applications, and/or workloadsto a virtualized cloud environment. The use of AWS migration servicesand tools, such as but not limited to, CloudEndure Migration, AWS ServerMigration Service (SMS) and AWS Migration Hub, are employed to assess,mobilize, migrate, and modernize the satellite communication basebandair interface system to the cloud based VSLAIS 201 variant.

In other embodiments, new or future satellite communication baseband airinterface systems can be developed into new versions of the VSLAIS 201directly within a native cloud computing environment.

The VSLAIS 201 operates in a similar manner to a traditional satellitebaseband air interface system with the same features and functionalityto effectively enable and manage the transmission and reception of alltypes of data to/from subscriber terminals. Such functionality ensurestelecommunications service delivery through use of attributes including,but not limited to, user data signals generation and reception, airinterface network management and functionality, addressing, bandwidthallocation and type, routing, quality of service, authentication,security, management, monitoring, provisioning, event logging, OSS/BSS,troubleshooting, etc.

Similarly, with traditional hardware (non-cloud) based satellitecommunications baseband air interface systems, there are multiplemethodologies that the VSLAIS 201 can employ to ensure user data signalsare transmitted and received from subscriber terminals effectively. TheCCGE 101 can support any of these methodologies for the specificsatellite communications baseband air interface system in a VSLAIS 201variant.

The VSLAIS 201 transmits and receives user data signals to and from avirtualized user data signal-spot beam controller (VUDSSBC) 203.

In some embodiments, the VSLAIS 201 transmits and receives user datasignals, and passes any specified associated management, control and/ormetadata, such as but not limited to, frequency, symbol rate, carrierspacing, roll-off factor, constant coding and modulation (CCM) oradaptive coding and modulation (ACM) details, to and from the VUDSSBC203.

The VSLAIS 201 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure. Multiple VSLAIS 201 variants are delivered via AWSproducts and services, such as but not limited to, Amazon ElasticCompute Cloud (EC2), Amazon Elastic Block Store (EBS), Amazon SimpleStorage Services (S3), and Amazon Relational Database Services (RDS).AWS products and services allows organizations to migrate workloads suchas applications, websites, databases, storage, physical or virtualservers, or entire data centers to the cloud. A traditional satellitecommunication baseband air interface system incorporates servers tocarry out the air interface networking and network management system(NMS) functions, these applications can run on the versatile EC2instances of varying types of compute capabilities including processor,core numbers and type, storage, network bandwidth and associated typeand quantity of memory. The VSLAIS 201 functionally stores multipleinformation technology components such as, but not limited to, softwareimages, run-time data and other non-RAM functional data. EBS can providemultiple service options for both hard disc drive (HDD) and solid statedrive (SSD) variants. Additionally, RDS services can support, operate,and scale a relational database in the cloud for the satellitecommunication baseband air interface system network statistics forstorage, retrieval, analysis, and reporting. Additionally, S3 objectstorage services can be utilized to store software images, backups,archives, and big data analytics.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the VSLAIS 201.

The VUDSSBC 203 manages the association of the user data signals to/froma single or plurality of VSLAISs to specific user spot beams (e.g., spotbeams 105, 106, and 107). The user spot beams can be configured for astatic fixed laydown configuration, in a dynamically changing real-timeenvironment or a hybrid of both.

The VUDSSBC 203 receives the transmit user data signals, and anyassociated metadata from a single or plurality of VSLAIS 201. TheVUDSSBC 203 groups specific transmit user data signals and associatedmetadata to a specific transmit forward user spot beam and sends theseto the virtualized digital modem, mapper and demapper (VDMMD) 204.

The VUDSSBC 203 accepts the receive user data signals from the VDMMD 204grouped within specific receive return user spot beams and distributesthem to the relevant associated VSLAIS 201. In some embodiments, theVUDSSBC 203 passes any metadata associated with the receive user datasignals from the VSLAIS 201 to the VDMMD 204.

The cloud computing gateway management and interface system (CCGMIS) 208can manage, control, and/or oversee the user spot beam laydownoperations. The CCGMIS 208 orchestrates and coordinates the subsystemsof the CCGE 200 under an encompassing and holistic view of the entireend-to-end communications system, that primarily incorporates the CCGE200 and satellite 100. The CCGMIS 208 orchestrates the user spot beamoperations and their associated user data signals utilizing knowledge onfactors such as, but not limited to, available RF spectrum resource,frequency re-use rules, preconfigured variables, autonomous controlvariables, rule based algorithms, priorities, bandwidth demand, resourceanalysis, performance analysis, satellite power, artificial intelligencemachine learning (AI/ML) insights, and/or other external factors andvariables.

In other embodiments, due to the flexibility of cloud computingresources, some/all of the core functions of the CCGMIS 208 arepermitted to be carried out by other sub-systems of the CCGE 200 and/orother external systems.

The VUDSSBC 203 manages a plurality of user spot beams and each may havewhatever total bandwidth in radio frequency (RF) is best suited for theapplication, contiguous or non-contiguous for both the transmit forwarduser spot beams and receive return user spot beams.

In other embodiments, the VUDSSBC 203 can additionally support broadcastand multicast transmit user data signals and map them to multiple or alltransmit forward user spot beams.

In some embodiments, the transmit forward user spot beams to thesubscriber terminals have five hundred megahertz (500 MHz) contiguousavailable RF spectrum, and the receive return user spot beams from thesubscriber terminals have two hundred fifty megahertz (250 MHz)contiguous available RF spectrum.

The VUDSSBC 203 transmits and receives the user spot beam configurationswith the associated user data signals, to/from the VDMMD 204.

The VUDSSBC 203 passes the transmits forward user spot beamconfigurations containing the associated forward user data signals andassociated metadata (such as but not limited to frequency, symbol rate,carrier spacing, roll-off factor, CCM and/or ACM) to the VDMMD 204.

The VUDSSBC 203 accepts the receive return user spot beamsconfigurations containing the associated return user data signals fromthe VDMMD 204, disaggregates and passes the specific return user datasignals to the appropriate VSLAIS 201. The VUDSSBC 203 passes anymetadata relating to the specific return user data signals and receivereturn user spot beams (such as but not limited to frequency, symbolrate, carrier spacing, roll-off factor, CCM and/or ACM) from the VSLAIS201 to the VDMMD 204, to allow effective demodulation of return userdata signals.

In other embodiments, metadata initiating from a VSLAIS 201 by the VDMMD204 can be passed directly or other means without the need of theVUDSSBC 203, as long as this task, when needed, is carried out.

The VUDSSBC 203 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure. The VUDSSBC 203 can be delivered via AWS products andservices, such as but not limited to, EC2, EBS, S3, and RDS. The VUDSSBC203 incorporates servers to carry out the user spot beam management andcontrol functions, these applications can run on versatile EC2 instancesof varying types of compute capabilities including processor, corenumbers and type, storage, network bandwidth and associated type andquantity of memory.

In some embodiments, the VUDSSBC 203 functionally stores multipleinformation technology components such as, but not limited to, softwareimages, run-time data and other non-RAM functional data. EBS can providemultiple service options for both HDD and SSD variants. Additionally,RDS services can support, operate, and scale a relational database inthe cloud for the spot beam system statistics for storage, retrieval,analysis, and reporting. Additionally, S3 object storage services can beutilized to store software images, backups, archives, and big dataanalytics.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the VUDSSBC 203.

The VDMMD 204 allows user data signals grouped within the user spotbeams to be created, manipulated, and extracted digitally to/from thedigital (non-analog) RF domain. The VDMMD 204 can be operator configuredwith multiple parameters, such as but not limited to, signal samplingand rates, I/Q data, amplification, and conditioning. In someembodiments, the VDMMD 204 can utilize the Vita 49 standard for digitalRF data signals.

The VDMMD 204 creates digitized RF carrier waves (of variousfrequencies, bandwidths and amplitudes) and modulates/maps them with thebaseband forward link user data signals within each forward link userspot beam.

The VDMMD 204 extracts the baseband return link user data signals withineach return link user spot beam by demodulating/demapping digitized RFsignals.

In other embodiments, the VDMMD 204 can employ additional digital signalprocessing and signal manipulation techniques, such as but not limitedto, amplification, conditioning, interference removal, jamming detectionand mitigation etc., to improve and optimize performance of thedigitized RF signals and the performance of the end-to-end satellitecommunications network.

In some embodiments, the VDMMD 204 utilizes metadata provided by theVSLAIS 201 and the VUDSSBC 203 to carry out the functions of convertingthe user data signals.

In some embodiments, the VDMMD 204 utilizes the MATLAB computingenvironment running on the cloud infrastructure to carry out the digitalsignal processing (DSP) tasks of converting to/from digitized RF based.

The VDMMD 204 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure.

In some embodiments, the VDMMD 204 is delivered via AWS products andservices, such as but not limited to, EC2, EBS, S3, and RDS. The VDMMD204 incorporates servers to carry out the RF signal digitizationcreation functions, these applications can run on versatile EC2instances of varying types of compute capabilities including processor,core numbers and type, storage, network bandwidth and associated typeand quantity of memory. The choice of EC2 types for the VDMMD 204 canrange from basic general purpose processing (GPP) to high performancecomputing (HPC) such as, but not limited to, to CPUs in a clusteredenvironments or FPGA instances to enable delivery of custom hardwareacceleration (e.g., AWS EC2 F1 services), and is dynamically selectableby the operator of the system depending on workload and performancedesired.

In some embodiments, VDMMD 204 functionally stores multiple informationtechnology components such as, but not limited to, software images,run-time data, other non-RAM functional data and data lakes. EBSprovides multiple service options for both HDD and SSD variants.Additionally, S3 object storage services can be utilized to storesoftware images, backups, archives, and big data analytics. S3 can alsobe utilized to store digitized RF data lakes for real-time andpost-operative analysis.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the VDMMD 204.

The VDMMD 204 sends the forward link user spot beam digitized RF signalsand receives the return link user spot beam digitized RF signalsrespectively to a virtualized on-ground beamformer (VOGB) 206 via avirtualized packet based radio transport (VPBRT) 205.

In the preferred embodiment, the VDMMD 204 functions occur between theVUDSSBC 203 and the VOGB 206 for simplicity and efficiency. Otherembodiments permit the digitized RF modulation, demodulation, mappingand demapping functions to be carried out in a different order. In someembodiments the VDMMD 204 functions can be carried out between theVSLAIS 201 and the VUDSSBC 203. In one such embodiment the VUDSSBC 203receives and sends digitized RF signals from/to the VSLAIS 201, thus thesingle or plurality of VSLAISs are responsible for their own individualdigitized RF signal creations and interpretations, and the VUDSSBC 203groups digitized RF user data signals to/from the appropriate spotbeams. Irrespective of where the VDMMD 204 resides, the transport ofdigitized RF signals between sub-systems within the CCGE 200 may bedelivered by core cloud computing networking services and/or othertechnologies that can ensure digitized radio signal transport integrityand fidelity, such as but not limited to, Vita 49 radio transportprotocol.

The CCGE 200 interfaces with a single or plurality of satellites, in thedigital domain utilizing digitized RF signals for the primary functionof the end-to-end satellite communications system. The digitized RFsignals are sent to/from different sub-systems and their associated VMs,instances and/or other cloud resources within the CCGE 200, and betweenthe CCGE 200 and the satellite (FIG. 3, 300).

The VPBRT 205 ensures the effective transmission and reception ofdigitized RF signals across a digital packet switched network andadditionally ensures digitized RF signal integrity, including but notlimited to signal fidelity, timing, and synchronization.

On the forward link direction, the VPBRT 205 packetizes digitized RFsignals in data packets (DP) for transmission over a digital switchednetwork. Additionally, the VPBRT 205 augments the significance of thesedigitized RF signal streams by coupling them to critical informationabout the RF signals with metadata encapsulated in metadata packets(MP). The MP contain context information and operating parameters foreach data packet stream.

Radio transport DP and MP form the radio transport information streams(IS) that are transported to an end point for signal reconstructionand/or processing, either in a virtualized and/or analog physical form.

On the return link direction, the VPBRT 205 depacketizes digitized RFsignals within IS that include their respective DP and MP received overa digital switched network.

The VPBRT 205 utilizes the MP containing context information andoperating parameters for DP stream to reconstruct the digitized RFsignal with predetermined and configured level of fidelity. In anon-limiting example, the use of the Vita 49 standard from the VitaStandards Organization (VSO) for the packet based radio transportprotocol (RTP) can be employed.

In other embodiments, other packet based radio transport standards orproprietary packet based radio transport can be utilized with additionalfeatures and/or services, such as but not limited to, increased control,status, operation, and configuration information.

The VPBRT 205 is a protocol for end to end radio transport. The VPBRT205 should include source and destination points in order to runinteroperable versions of the protocol. The prime function of the RTP isto transport digitized RF signals between the satellite 300 and the CCGE200. In some embodiments, the VPBRT 205 can be utilized to transportdigitized radio signals between different subsystems within the CCGE 200to ensure digitized radio signal transport integrity and fidelity, andin some embodiments specifically between the VDMMD 204 and VOGB 206.Thus, the VPBRT 205 can represent at least two instances, one residingin sufficient proximity to the VDMMD 204 and the other residing insufficient proximity to the VOGB 206, each transmitting and receivingrespective IS. As such, the close proximity ensures digitized radiosignal integrity and fidelity when traversing localized cloud computingresources.

The sub-systems of the CCGE 200 can be collocated for simplicity,however other embodiments permit the geographic dispersity ofsub-systems if so desired.

In some embodiments, the transport of digitized RF signals betweensub-systems within the CCGE 200 may be delivered by core cloud computingnetworking services and/or other technologies that can ensure digitizedradio signal transport integrity and fidelity. Thus, in such anembodiment the VPBRT 205 is negated between the VDMMD 204 and VOGB 206and IS are transferred directly over a CCDSN 210 capable of ensuringdigitized RF signal transport with integrity and fidelity.

Other embodiments permit both the VDMMD 204 and VPBRT 205 to co-existtogether on the same cloud computing compute instance(s) and associatedresources. Further embodiments permit the VOGB 206 and VPBRT 205 toco-exist together on the same cloud computing compute instance(s) andassociated resources.

The VPBRT 205 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure. In some embodiments, the VPBRT 205 is delivered via AWSproducts and services, such as but not limited to, EC2, EBS, and S3. TheVPBRT 205 incorporates servers to carry out the RTP functions, theseapplications can run on versatile EC2 instances of varying types ofcompute capabilities including processor, core numbers and type,storage, network bandwidth and associated type and quantity of memory.

In some embodiments, VPBRT 205 functionally stores multiple informationtechnology components such as, but not limited to, software images,run-time data, and other non-RAM functional data. Additionally, S3object storage services can be utilized to store software images,backups, archives, and big data analytics.

In some embodiments, the VPBRT 205 utilizes AWS core networking servicessuch as, but not limited to, AWS Transit Gateway and Amazon Route 53.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the VDMMD 204.

The virtualized on-ground beamformer (VOGB) 206 provides the ability tocreate the plurality of various sized, flexible, adaptive forward andreturn link user spot beams on the Earth, known as a laydown, thatencompass and carry the uniquely assigned forward and return link userdata signals. Flexibility in the satellite communication system allowsthe user spot beam laydown to be fixed or to change dynamically, evendown to a sub-second by sub-second basis.

The VOGB 206 calculates, produces, or otherwise obtains phase andamplitude coefficients for each forward and return link user spot beamsignal for all (or a subset of) spacecraft antenna elements (FIGS. 3,309 and 310), and thus carries out the beamforming functions for theforward and return links. The VOGB 206 creates unique forward linkdigitized RF transmit antenna element signals and receives unique returnlink digitized RF receive antenna element signals for processing. TheVOGB 206 performs the beamforming analysis and computation in thedigital domain with digitized RF signals.

In other embodiments, the VOGB 206 can utilize alternate beamformingtechnologies and methods such as, but not limited to, the use ofcalibration subsystems that utilize reference remote terminals.

The VOGB 206 can operate and support analog, digital, and/or hybridbeamforming operation through the virtualized environment.

In some embodiments, the VOGB 206 employs digital beamforming creatingdifferent signals designed for each of the spacecraft antenna elementsin the digital domain allowing for greater flexibility since one canassign different powers and phases to different antenna elements and todifferent parts of the frequency bands. This makes digital beamformingparticularly desirable for user spot beam laydown and beneficial whenhaving a wide bandwidth because with fixed phases and/or amplitude thesignal will get a different directivity in different parts of the band.

In some embodiments, the VOGB 206 creates a single forward linkinformation stream (IS) per transmit antenna element and receives asingle return link IS per receive antenna element. In other embodiments,the VOGB 206 may utilize a subset of the transmit antenna elementsand/or receive antenna element.

In some embodiments, the satellite antenna system (FIGS. 3, 309 and 310)utilizes 250 transmit antenna elements (TAE) (FIG. 3, 309) for each oftwo transmit polarizations V/H or L/R, hence 500 total TAEs; and 250receive antenna elements (RAE) (FIG. 3, 309) for each of two receivepolarizations V/H or L/R, hence 500 total RAEs. Other embodiments canutilize whatever number of TAEs and RAEs is configured and/or specifiedin the satellite antenna system by the satellite manufacturer, owner,operator, and/or other. The higher the number of antenna elements in thesystem, the higher the number of IS, and hence a higher total ISthroughput is associated for similar sampling and resolution rates ofthe digitized signals.

The VOGB 206 sends the forward link digitized feed element signals toand receives the return link digitized feed element signals from, aground optical communications feeder link system (GOCFLS) 207 via asecond VPBRT 211. In some embodiments, the VPBRT 211 is beneficially(and sometimes critically) located within sufficient proximity to theVOGB 206 within the CCGE 200 to ensure digitized radio signal integrityand fidelity when traversing localized cloud computing resources.Further, the second VPBRT 211 can be implemented in the same manner andmethod as the first VPBRT 205.

Other embodiments permit both the VOGB 206 and VPBRT 211 to co-existtogether on the same cloud computing compute instance(s) and associatedresources.

The VOGB 206 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure.

In some embodiments, the VOGB 206 is delivered via AWS products andservices, such as but not limited to, EC2, EBS, and S3. The VOGB 206 canrun on versatile EC2 instances of varying types of compute capabilitiesincluding processor, core numbers and type, storage, network bandwidthand associated type and quantity of memory.

In some embodiments, the choice of EC2 types for the VOGB 206 can rangefrom basic general purpose processing (GPP) to high performancecomputing (HPC) such as, but not limited to, to CPUs in a clusteredenvironments or FPGA instances to enable delivery of custom hardwareacceleration (e.g., AWS EC2 F1 services), and is dynamically selectableby the operator of the system depending on workload and performancedesired.

AWS HPC integrated suite of services provides the infrastructure neededto build and manage compute clusters in the cloud to run the mostintensive workloads quickly and easily. In some embodiments, the VOGB206 delivers digital beamforming with options available to the digitalbeamforming algorithms employed and the associated level of computationand computation resources desired.

In some embodiments, VOGB 206 functionally stores multiple informationtechnology components such as, but not limited to, software images,run-time data, other non-RAM functional data and data lakes. EBS canprovide multiple service options for both HDD and SSD variants.Additionally, S3 object storage services can be utilized to storesoftware images, backups, archives, and big data analytics. S3 isutilized to store digitized RF data lakes for real-time andpost-operative analysis.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the VOGB 206.

The CCGE 200 connects to a single or plurality of satellites (FIG. 3,300) via a single or plurality of GOCFLS 207.

In the preferred embodiment, the GOCFLS 207 provides the digitalcommunications link to/from the satellite (FIG. 3, 300) and thus extendsthe digital switched network to the satellite 300. A free space opticalcommunication system is chosen for the feeder link between the CCGE 200and the satellite (FIG. 3, 300) due to its high data throughputcapability associated for the transport of multiple VPBRT 211 ISsessions.

An optical communication system is chosen over any RF system, even atQ/V band, as RF does not possess equivalent capacity to support highthroughput satellites (HTS), very high throughput satellites (VHTS) andvery very high throughput satellites (VVHTS), which is known as ultrahigh throughput satellites (UHTS).

The GOCFLS 207 carries out the transmission and reception of datasignals between the CCGE 200 and the satellite (FIG. 3, 300).

In the preferred embodiment, the primary task of the GOCFLS 207 is totransport IS to/from the CCGE 200 and the spacecraft (FIG. 3, 300).

In other embodiments, the GOCFLS 207 can also be used to transport otherdata to/from the satellite 300, such as but not limited to Telemetry,Tracking and Command (TT&C), Command & Data Handling (CD&H) information,and firmware and other software upgrades to the satellite 300.

In some embodiments, the GOCFLS 207 utilizes a Tbps capacitybi-directional ground-space/space-ground optical communications system.Other embodiments can utilize other variants of lower throughputcapacity such as one hundred Gigabits per second (100 Gbps).

In some embodiments, the GOCFLS 207 Tbps capacity is delivered through asingle optical ground station using dense wavelength divisionmultiplexing (DWDM) techniques as known from terrestrial fibercommunications.

The CCGE 200 and GOCFLS 207 link to the satellite 300 willintermittently experience blockage by weather clouds, other atmosphericeffects and/or other local operational issues, such as but not limitedto, power outages and CDC catastrophic failures etc., and thus will becompensated by CCGE 200 and GOCFLS 207 diversity. The bi-directionalground-space/space-ground optical communications system is primarilyaffected by factors, such as but not limited to, scintillation and beamwander induced by the atmospheric index-of-refraction turbulence. TheGOCFLS 207 utilizes capabilities, such as but not limited to, mitigatingof these distortions by an according high-speed tracking and fadingcompensation techniques.

In some embodiments, the GOCFLS 207 utilizes adaptive optics (AO) tomitigate many of the atmospheric turbulence effects. In otherembodiments, the GOCFLS 207 can utilize other physical and frame layertechnologies to ensure the specified 100's Gbps, Tbps and above freespace bi-directional throughput.

The ground-space/space-ground optical communications system can besusceptible to localized atmospheric effects, such as but not limitedto, rain-fade, turbulence and/or other scintillation effects. As such,the ability to switch back and forth between different geographicallydispersed CCGEs and associated GOCFLSs is permitted.

When the specific localized atmospheric effects restrict operation of aspecific CCGE and its GOCFLS, the system is switched to another CCGE andits GOCFLS under more favorable conditions conducive to effectiveoperations.

The GOCFLS 207 can be either collocated with the CCGE 200, or at anotherlocation connected via a digital switched network, such as but notlimited to, fiber optical links.

In some embodiments, a plurality of GOCFLSs and CCGEs are utilized forresiliency and higher specified total satellite communication systemavailability. However, the satellite communication system is optimizedto utilize as few geographically dispersed CCGEs and their associatedGOCFLSs as possible whilst maintaining a specified availabilitypercentage.

A specific satellite 300 is typically serviced by only one CCGE 200 andassociated GOCFLS 207 for normal service operation at any instant.However, in some embodiments, the use of a feeder link make-before-breaksystem is employed to allow seamless switchover between a plurality ofgeographically dispersed CCGEs and their associated GOCFLSs, to maximizethe satellite communication system availability. In some embodiments,the satellite 300 is equipped with multiple space optical communicationfeeder link systems (SOCFLS) (FIG. 3, 301), allowing each to connect toa different set of CCGE and GOCFLS configurations.

In other embodiments where the satellite 300 has a single SOCFLS 301,diversity is provided through an active and hot standby operation ofgeographically dispersed CCGEs and their associated GOCFLSs, where oneCCGE/GOCFLS is active and another CCGE/GOCFLS is in hot standby modeready to switch in when it becomes beneficial.

The CCGE 200 and the GOCFLSs communicate using a CCDSN 210. In theembodiments where the GOCFLS 207 is not collocated with the CCGE 200,the CCDSN 210 can extent from within the cloud computing infrastructureover external public or private networks to where the GOCFLS 207 arelocated geographically.

A single CCGE at a CDC may be supported by a single or plurality ofGOCFLSs 207 that are collocated and/or geographically dispersed. In someembodiments, where the CCGE 200 is supported by geographically dispersedGOCFLSs 207, a wide area network (WAN) can be used for the connectionand to extend the packet switched networking from the CCGE 200 to eachof the GOCFLSs 207.

In embodiments where a plurality of geographically dispersed CCGEs 200and their CDCs each with its own GOCFLS and/or pool of GOCFLSsco-located or otherwise, are employed, the system is optimized when theonline CCGE and its associated VMs, cloud computing instances and othercloud resources are activated as/when the specific CCGE is beneficialfor operation. Further embodiments allow multiple CCGEs to be activeduring a make-before-break operation with only one GOCFLS active at anyinstant.

Although the primary embodiment details the CCGE 200 connecting to thesatellite (FIG. 3, 300) via the GOCFLS 207, a CCGE can scale and supporta plurality of satellites where the sub-systems of the CCGE 200 areduplicated at a particular CDC, and where the particular CDC isconnected and supported by multiple GOCFLSs, one for each satelliteoperated and supported.

In some embodiments, the end-to-end satellite communications system andall sub-systems are orchestrated and monitored by the means of theCCGMIS 208. The CCGMIS 208 interfaces with all or a subset of theend-to-end satellite communication sub-systems, including both theground and space segment. In other embodiments, other orchestrationsystems can be employed utilizing a mixture of private and/or publiccloud and/or other on-premises based management systems.

In further embodiments, sub-systems of the CCGE 200 can utilize theirown network management systems (NMS) and/or their own control systems(CS) either within a single or plurality of VMs, instance(s) and othercloud resources, or within a traditional on-premises server applicationenvironment that connects to the CCGE 200. The NMSs and/or CSscommunicate management, configuration, and operations informationto/from the sub-systems of the CCGE 200, under the high-levelorchestration of the CCGMIS 208. A single or plurality CCGMISs 208 canbe utilized in a master and slave(s) configuration.

In some embodiments, the CCGMIS 208 is collocated at the same CDC as theCCGE 200. In other embodiments the CCGMIS 208 can be operating fromdifferent CDCs with or without an active CCGE to satellite link.

In some embodiments, the CCGMIS 208 manages and controls the switchingfrom one CCGE 200 to another to provide resiliency in the end-to-endsatellite communications system.

The CCGMIS 208 is performed through a single or plurality of VMs,instances, services and resources running on the cloud computinginfrastructure. In some embodiments, CCGMIS 208 is delivered via AWSproducts and services, such as but not limited to, EC2, EBS, S3, andRDS. The CCGMIS 208 functionally stores multiple information technologycomponents such as, but not limited to, software images, run-time dataand other non-RAM functional data. EBS can provide multiple serviceoptions for both HDD and SSD variants. Additionally, RDS services cansupport, operate, and scale a relational database in the cloud for theCCGMIS 208 statistics for storage, retrieval, analysis, and reporting.Additionally, S3 object storage services can be utilized to storesoftware images, backups, archives, and big data analytics.

In other embodiments, other cloud service combinations and/or additionalservices of AWS or other CSPs and cloud vendors, can be employed tocreate and operate the CCGMIS 208.

Space Segment

FIG. 3 depicts the block diagram of the space segment component of thesatellite communication system.

The satellite 300 will include multiple additional bus components (notshown in the diagram), including but not limited to, power sources, suchas batteries, solar panels and one or more propulsion systems, for thegeneral operation of the bus and the payload.

The satellite 300 communicates with the GOCFLS (FIG. 2, 207) via asingle or plurality of SOCFLS 301.

In some embodiments, the SOCFLS 301 is designed to be compatible withthe GOCFLS (FIG. 2, 207) and to place a higher burden of maintaining thebi-directional Tbps link on the GOCFLS 207, resulting in a reduced thesize, weight, power and cost (SWaPC) of the SOCFLS 301.

The primary task of the SOCFLS 301 is to transport the digitized forwardand return RF signals within their respective IS between the satellite300 and the CCGE (FIG. 2, 200), specifically between the on-boardprocessor: packet based radio transport (OBPPBRT) 304 and the VPBRT(FIG. 2, 211).

In other embodiments, the SOCFLS 301 can be used to transport any otherdata, such as but not limited to, telemetry, tracking and command (TT&C)data.

The SOCFLS 301 sends the multiple forward link IS and receives multiplereturn link IS to/from an on-board processor (OBP) 303 and its OBPPBRT304, via an on-board digital network distribution system (OBDNDS) 302.

The OBDNDS 302, performs all packet based digital networking activitiesbetween on-board sub-systems and components of the satellite 300.

In some embodiments, the OBDNDS 302 is achieved with fiber opticconnections and a plurality of fiber optic transceivers utilized atrespective end points. Other embodiments can utilize other packet baseddigital network and/or high-speed serial connection technologies.

The OBP 303 performs multiple tasks on-board the satellite, such as butnot limited to, packet based radio transport functions, routing,digital-to-analog conversion (DAC) and analog-to-digital conversion(ADC) and other payload management and control functions. In otherembodiments, the OBP 303 can be utilized to carry out spacecraft bushousekeeping operations, such as but not limited to, tracking, telemetry& control (TT&C) and command & data handling (CD&H).

The hardware implementation of the OBP 303 can be provided by means ofmultiple configuration embodiments. This can include, but not limitedto, the combinations of CPU, memory, ASIC, FPGA, clocking generators,and various Interfaces to optimize the size, weight and power, and cost(SWaPC) trade-offs for the satellite and its performance.

The OBPPBRT 304 ensures the effective transmission and reception offorward and return digitized RF signals within IS send to and from theSOCFLS 301. The OBPPBRT 304 carries out a similar function as the VPBRT(FIG. 2, 205), on board the satellite.

In the forward link direction, the OBPPBRT 304 depacketizes digitized RFsignals within data packets (DPs) and metadata packets (MP) receivedfrom a digital switched network.

The OBPPBRT 304 utilizes the MP containing context information andoperating parameters for each DP stream to reconstruct the digitized RFsignals with operator defined predetermined level of fidelity.

In the return link direction, the OBPPBRT 304 packetizes digitized RFsignals in data packets (DP) for transmission over a digital switchednetwork. Additionally, the OBPPBRT 304 augments the significance ofthese digitized RF signal streams by coupling them to criticalinformation about the RF signals with metadata encapsulated in metadatapackets (MP). The MP contain context information and operatingparameters for each DP stream.

Radio transport DP and MP form the radio transport IS that aretransported to an end point for signal reconstruction and processing,either in a virtualized or physical form.

In some embodiments, the Vita 49 standard from the Vita StandardsOrganization (VSO) for the radio transport packet based protocol isutilized.

In other embodiments, other packet based radio transport standards orproprietary variants can be utilized with additional features and/orservices, such as but not limited to, increased control, status andconfiguration information.

As the OBPPBRT 304 utilizes a protocol for end to end radio transport,the OBPPBRT 304 requires source and destination points to be runninginteroperable versions of the protocol.

The OBPPBRT 304 sends forward link digitized RF signals to a pluralityof on-board processor: digital-to-analog converters (OBPDAC) 305 andreceives return link digitized RF carriers from a plurality of on-boardprocessor: analog-to-digital converters (OBPADC) 306.

The OBPDAC 305 perform the conversion of each of the digitized RFsignals into a respective analog RF signal mapped to a specific TAE 309.

In some embodiments, the OBPDAC 305 utilizes RF softwarization andconverts the digitized RF signal IS to analog RF in the desired analogRF, such as but not limited to, S, L, Ku, Ka and/or C band, via directmicrowave digitization. The OBPDAC 305 can, in a non-limiting example,utilize system in package (SiP) technology to deliver the softwaredefined microwave (SDM) systems allowing the direct conversion fromdigital to analog RF, therefore placing the digital conversion closer tothe TAEs 309, and simplifying and reducing complex analog RF componentryand circuitry, such as but not limited to, filters, orthomode junctions,test couplers, upconverts, intermediate amplifiers etc.

Further, the OBPDAC 305 can employ direct synchronization technologiesacross the array of SiP DACs.

In other embodiments, the OBPDAC 305 can utilize other multiple DAC RFtechnologies to carry out the conversion of multiple digitized RFsignals to analog variants.

The output of the OBPDAC 305 is forwarded to a transmit RF distributionsystem (TRFDS) 307.

TRFDS 307 ensures that every analog RF signal is applied to theassociated physical TAE 309 on the antenna system.

The TRFDS 307 ensures the analog RF signals are amplified through theuse of monolithic microwave integrated circuit (MMIC) hardware thatprovide functions, such as but not limited to, microwave mixing, poweramplification, wideband power amplification, and/or high-frequencyswitching.

In other embodiments, the use of other RF conditioning and amplificationsystems is permitted in the TRFDS 307 to ensure that the analog RFsignals are kept to the operator desired level of operation between theOBPDAC 305 and the TAE 309, and ultimately between the OBPDAC 305 andthe subscriber terminals (STs). In other embodiments, the level ofcomplexity and performance of the TRFDS 307 varies with the number andtype of associated components depending on operator specifications.

The TAEs 309 and the rest of the transmit antenna can be collectivelyreferred to as the transmit antenna subsystem. The use of a feed arrayand reflector system can be employed. All or some of the TAEs 309 canshare a common reflector. Such reflectors is/are not shown in thediagrams for simplicity. The TAE 309 form a multiple element transmitantenna feed array. This multiple element transmit antenna feed array isused to form the downlink spot beams as created by the VOGB (FIG. 2,206).

In other embodiments, the use of other transmit element array antennatechnology such as, but not limited to, direct radiating antenna (DRA)technologies are permitted.

The TAEs 309 each transmit their unique analog RF signal that containsand forms all or a subset of the downlink user spot beams withassociated RF forward user data signals in the beamforming environment.

A plurality of RAE 310 and the rest of receive antenna can becollectively referred to as the receive antenna subsystem. The use of afeed array and reflector system can be employed. All or some of the RAEs310 can share a common reflector. Such reflectors is/are not shown inthe diagrams for simplicity. The RAEs 310 form a multiple elementreceive antenna feed array. This multiple element receive antenna feedarray is utilized by the VOGB (FIG. 2, 206) to form the uplink spotbeams.

In other embodiments, the use of other receive element array antennatechnology such as, but not limited to, direct receiving antenna (DRA)technologies are permitted.

The RAEs 310 each receive their unique analog RF signal that containsall or a subset of the uplink user spot beams with associated RF returnuser data signals in the beamforming environment.

The RAEs 310 forward their unique analog RF signals to respective OBPADC306 via a receive RF distribution system (RRFDS) 308.

The RRFDS 308 ensures that every analog RF signal from each of thephysical RAE 310 on the receive antenna system is forwarded to arespective OBPADC 306.

The RRFDS 308 ensures the receive analog RF signals are bandpassfiltered and amplified prior to being received by the OBPADC 306 throughthe use of monolithic microwave integrated circuit (MMIC) hardware thatprovide functions, such as but not limited to, microwave mixing, lownoise amplification, wideband low noise power amplification, low phasenoise amplification, tunable bandpass filtering and/or high-frequencyswitching.

In other embodiments, the use of other RF conditioning and amplificationsystems are permitted in the RRFDS 308 to ensure that the analog RFsignals are kept to the operator desired level of operation between theRAEs 310 and the OBPADC 306, and ultimately between the subscriberterminals (ST) and OBPADC 306. In other embodiments, the level ofcomplexity and performance of the RRFDS 308 varies with the number andtype of associated components depending on operator specifications.

The OBPADC 306 perform the conversion of each of the analog RF signalsinto a respective digitized RF signal mapped from a specific RAE 310.

In some embodiments, the OBPADC 306 utilizes ultra-wideband (UWB) RFsoftwarization and converts the analog RF signal in the desired analogRF, such as but not limited to, S, L, Ku, Ka and/or C band, to adigitized RF signal via direct microwave digitization. The OBPADC 306can utilize system in package (SiP) technology to deliver the softwaredefined microwave (SDM) systems allowing the direct sampling from analogto digital RF, therefore placing the digital conversion closer to theRAEs 310, and simplifying and reducing complex analog RF componentry andcircuitry, such as but not limited to, filters, orthomode junctions,test couplers, downconverters, filters, and/or intermediate amplifiersetc.

Further, the OBPADC 306 can additionally employ direct synchronizationtechnologies across the array of SiP ADCs.

In other embodiments, the OBPADC 306 can utilize other multiple ADC RFtechnologies to carry out the conversion of multiple analog RF signalsto digitized variants.

The OBPADC 306 forwards the digitized RF signals from all or a subset ofthe RAEs 310 and via the OBPPBRT 304, OBDNDS 302, SOCFLS 301 and theGOCFLS (FIG. 2, 207) to the CCGE (FIG. 2, 200).

Operation

Forward Link

FIG. 2 and FIG. 3 help describe the portion of the forward link systemand equipment according to an embodiment of the present technology.

The VSLAIS 201 manages the network operations for the communication airinterface and enables the user data to couple to external network(s) 202such as, for example, the Internet, terrestrial public switchedtelephone network, mobile telephone network or private server network(s)etc.

In the forward link direction, the VSLAIS 201 receives data from theexternal networks 202 and creates appropriate forward link user datasignals under the parameters controlled by the network management system(NMS) of the specific air interface(s) in operation. The VSLAIS 201 andits associated NMS additionally functions under the guidance of theCCGMIS 208 receiving management, control and configuration parametersrelating to the forward link user data signals.

The VSLAIS 201 outputs the forward link user data signals and associatedmanagement and control, and/or metadata to the VUDSSBC 203 utilizing theCCDSN 210. The VSLAIS 201 is configured and operated in a similar mannerto any traditional non-cloud based satellite communications airinterface by the operator, wholesale service provider, and/or virtualnetwork operator (VNO) customer.

The VUDSSBC 203 receives the forward link user data signals (andassociated management and control, and/or metadata) in a single orplurality of bit stream format(s) from the single or plurality ofVSLAISs 201, and packages them together within the appropriate forwardlink user spot beam data signals. The VUDSSBC 203 functions under theguidance of the CCGMIS 208 that controls all the specific spot beams andprovides their specific configurations, such as but not limited to, themapping of the forward link user data signals to the associated forwardlink user spot beam(s).

The VUDSSBC 203 outputs the forward link user spot beam data signals tothe VDMMD 204 utilizing the CCDSN 210.

The VDMMD 204 creates digitized RF carrier waves in the desired RF ofthe forward link user spot beams, and digitally modulates and maps thebit streams according to the modulation and coding schemes determined bythe VSLAIS 200 for each forward user data signal within a forward linkuser spot beam data signal. The VDMMD 204 creates and outputs a forwardlink digitized RF user spot beam signal for each spot beam to the VOGB206 utilizing the VPBRT 205 and the CCDSN 210.

The VOGB 206 performs the beamforming functions on all the forward linkdigitized RF user spot beam signals received from the VDMMD 204.

The VOGB 206 carries out its tasks on the forward link digitized RF userspot beam signals under the guidance of the CCGMIS 208 that controls thespot beams and provides their specific configurations, such as but notlimited to, the size, dimensions, locations, and/or other operationalparameters of the forward link user spot beams.

For each forward link digitized RF user spot beam signal, the VOGBcalculates, produces or otherwise obtains the phase and amplitudecoefficients for all (or a subset) of the satellite TAEs 309. The VOGB206 takes each forward link digitized RF user spot beam signal andcreates multiple variants with their respective coefficients applied,one for each of the TAEs 309. The VOGB 206 then sums all the individualforward link digitized RF user spot beam signals variants for eachspecific TAE 309 producing a unique forward link digitized RF TAEsignal.

In some embodiments, the VOGB 206 can assign different power and phasecoefficients to a single or plurality of segments of the frequency bandswithin the forward link digitized RF user spot beam signals.

In other embodiments, alternate beamforming technologies and/or methodscan be utilized including but not limited to, the use of calibrationsubsystems with reference remote terminals.

The VOGB 206 then utilizes the VPBRT 211 to transport each forward linkdigitized RF TAE signal within data packets (DP) and associated metadatapackets (MP) forming individual IS. The multiple IS are forwarded to theGOFLCS 207 via the CCDSN 210.

The GOCFLS 207 relays and transmits the IS to the SOCFLS 301. The GOCFLS207 and SOCFLS 301 perform all optical laser communications physical andlink layer operations. In other embodiments, high layer functionality ispermitted between the GOCFLS 207 and the SOCFLS 301 to ensure maximumeffectiveness in transferring the IS.

The SOCFLS 301 receives the multiple IS containing forward linkdigitized RF TAE signals. The SOCFLS 301 forwards the IS by means of theOBDNDS 302 to the OBPPBRT 304.

The OBPPBRT 304 receives the IS and depacketizes the DP and MP andreconstructs the individual forward link digitized RF TAE signals. TheOBPPBRT 304 passes the multiple forward link digitized RF TAE signalsand their associated metadata to the OBPDACs 305.

Each of the OBPDAC 305 performs the conversion of the forward linkdigitized RF TAE signals into a respective forward link analog RF TAEsignal and passes them to the TRFDS 307.

The TRFDS 307 maps the forward link analog RF TAE signal output of eachof the OBPDAC 305 to its specific and assigned TAE 309, which thentransmits the signal.

The plurality of TAEs 309 form a multiple element antenna feed systemand form spot beams as controlled by the VOGB 206. The multiple spotbeams are then received by the appropriate subscriber terminals (ST).

Return Link

FIG. 2 and FIG. 3 help describe the portion of the return link systemand equipment according to an embodiment of the present technology.

The RAEs 310 receive their own variant of the return link analog RF RAEsignals that are transmitted by the subscriber terminals (ST) to thesatellite.

Each RAE 310 distributes its specific return link analog RF RAE signalto the RRFDS 308.

The RRFDS 308 connects each RAE to a respective OBPADC 306. Each OBPADC306 then converts each return link analog RF RAE signal to a return linkdigitized RAE signal. The OBPADC 306 sends the return link digitized RAEsignals to the OBPPBRT 304.

OBPPBRT 304 converts each return link digitized RAE signal to a uniqueIS with associated DP and MP. The OBPPBRT 304 passes the multiple returnlink IS to the SOCFLS 301 via the OBDNDS 302.

The SOCFLS 301 transmits the multiple IS to the operational GOCFLS 207.The SOCFLS 301 and GOCFLS 207 carry out all optical laser communicationsphysical and link layer operations. In other embodiments, high layerfunctionality is permitted between the GOCFLS 207 and the SOCFLS 301 toensure maximum effectiveness in transferring the IS.

The operational GOCFLS 207 receives the multiple IS from the SOCFLS 301and relays them to the VPBRT 211 via the CCDSN 210.

The VPBRT 211 receives the multiple IS and depacketizes the DP and MP toreconstruct the return link digitized RAE signals. The VPBRT 211 sendsthe return link digitized RAE signals to the VOGB 206.

The VOGB 206 takes each return link digitized RAE signal and calculates,produces or otherwise obtains phase and amplitude coefficients for eachreturn link user spot beam per every RAE and performs the computationand the summation processes to extract the return link digitized RF userspot beam signals for each spot beam.

In some embodiments, the VOGB 206 can assign different power and phasecoefficients to a single or plurality of segments of the frequency bandswithin the return link digitized RF user spot beam signals.

The VOGB 206 carries out its tasks on the return link digitized RAEsignals under the guidance of the CCGMIS 208 that controls the spotbeams and provides their specific configurations, such as but notlimited to, the size, dimensions, locations, and/or other operationalparameters of the return link user spot beams.

In other embodiments, alternate beamforming technologies and managementmethods can be utilized including but not limited to, the use ofcalibration subsystems.

The VOGB 206 forwards the return link digitized RF user spot beamsignals to the VPBRT 205 which utilizes IS to forward the return linkdigitized RF user spot beam signals to the VDMMD 204. The VDMMD 204digitally demodulates and demaps the return link digitized RF user spotbeam signals to output the return link user data signals to the VUDSSBC203. The VDMMD 204 operates under the guidance of the VUDSSBC 203 whichin turn utilizes information from the VSLAIS 201.

The VUDSSBC 203 outputs the specific return link user data signals tothe specific VSLAIS 201.

The VSLAIS 201 connects the return link user data to the coupledexternal network(s) 202 such as, for example, the Internet, terrestrialpublic switched telephone network, mobile telephone network or privateserver network(s) etc.

Gateway Switching

FIG. 4 helps describe the portion of the gateway switching operationaccording to an embodiment of the present technology.

In some embodiments, the CCGMIS ensures the switching management,control, and operation between multiple CCGEs and their associatedGOCFLSs.

The CCGMIS monitors and controls the feeder link resiliency system wherea single or plurality of CCGEs and their respective GOCFLSs ensureoperator specified availability of the feeder link system to thesatellite (FIG. 3, 300). The CCGMIS controls when one CCGE and/or GOCFLSswitches in for another in a resiliency situation.

In some embodiments all the CCGMISs (CCGMIS 208_1, CCGMIS 208_2 . . .CCGMIS 208_n) may be online with one designated as master and the othersdesignated as slaves. There is no limit on the total number of CCGMISs.The CCGMIS collocated with the active CCGE and its associated GOCFLSshall assume the role of master. While the active CCGE and itsassociated GOCFLS is in operation serving the satellite, the otherCCGE's sub-systems (e.g., VSLAISs, VUDSSBC, VDMMD, VPBRTs and VOGB) canbe rendered dormant utilizing minimum active cloud computing resourceuntil called upon. In this embodiment, the CCGMISs are the only activesub-system at all the CCGEs. In other embodiments a subset of CCGMISsmay only be active.

The CCGMISs 208_n (master and slave(s)) maintain shared configurationand parameters and can update each other to enable a fully active CCGEas/when called upon.

In this embodiment the use of a high available, and low-latency privateglobal network infrastructure (PGNI) 400 is utilized between theindividual CDCs and their associated CCGEs. The PGNI 400 is built on aglobal, fully redundant, parallel high speed fiber network that islinked intra-continent and inter-content via multiple technologies,including but not limited to, trans-oceanic cables. In otherembodiments, the use of other technologies and geographical coveragelinking CDCs and CCGEs is permitted to allow desired level ofoperational metrics.

In example, CCGE 200_1 is currently active and operationally supportingthe end-to-end satellite communications system, and hence CCGMIS 208_1is the master responsible for carrying out the switching functions toanother CCGE with its associated GOCFLS when resiliency requires so.When CCGMIS 208_1 determines that CCGE 200_2 will now be better placedto carry out the operation and support of the end-to-end satellitecommunications system, CCGMIS 208_1 instructs CCGMIS 208_2 to initiateand activate all the CCGE 200_2 sub-systems (e.g., VSLAISs, VUDSSBC,VDMMD, VPBRTs and VOGB). Once the cloud computing resources andinstances are activated and enabled at CCGE 200_2, the switchover isperformed. At this point CCGMIS 208_2 will assume the role of masterCCGMIS and therefore the process continues.

In other embodiments, a subset of CCGEs or partial CCGEs is permitted tobe initiated to allow for faster and more seamless switching betweenCCGEs if beneficial and/or required. Such embodiments can see a dynamicallocation of CCGE cloud computing resources being activated anddeactivated in real time.

The CCGMISs can additionally control the switch and transition toanother GOCFLS that is either directly connected to the same CDC andCCGE.

In this embodiment the CCGMISs utilizes information provided by theactive GOCFLS and/or the SOCFLSs detailing the active optical linkperformance, and/or other data and information pertaining to thelocalized conditions of all the GOCFLSs, such as but not limited to,localized atmospheric conditions, doppler radar, satellite weatherinformation, predictive weather analytics and modelling etc., to makethe most effective decision of which of the geographically dispersedGOCFLSs and associated CCGE is best suited to serve the end-to-endsatellite communications system.

In further embodiments, the inactive GOCFLSs are permitted to test theirrespective optical links to the satellite via the redundant SOCFLS in around-robin and repeating operation, thus providing real-time andempirical link performance data to the CCGMISs.

Dynamic Multi Air Interface Operation

FIG. 5 helps describe the portion of the dynamic multi air interfaceoperation according to an embodiment of the present technology.

In this embodiment, the CCGE 200 supports a plurality of VSLAISs andplurality of operational configurations of VSLAISs. In example, VSLAIS201_1, VSLAIS 201_2 and VSLAIS 201_3 are operational and VSLAIS 201_4,VSLAIS 201_5 through VSLAIS 201_n are dormant utilizing minimal or zeroactive cloud computing resource until called upon.

The CCGMIS 208 coordinates the activation, coordination, anddeactivation of the VSLAISs under operator configured parameters,real-time metrics, and/or factors such as, but not limited to,pre-configured scheduling, available RF spectrum resource, frequencyre-use rules, preconfigured variables, autonomous control variables,rule based algorithms, priorities, bandwidth demand, resource analysis,performance analysis, satellite power, artificial intelligence machinelearning (AI/ML) insights, and/or other external factors and variables.

The CCGMIS 208 can orchestrate multiple VSLAIS combinations andpermutations in a static, scheduled, and/or dynamic real-timeenvironment.

The CCGMIS 208 additionally can control the VSLAIS operationalparameters when active to maintain operator defined performance acrossthe entire end-to-end satellite communications system, such as but notlimited to, carrier numbers, carrier sizes, carrier parameters, spotbeam assignments, beamhopping assignments, and/or RF transmit powerlevels.

ALTERNATIVE EMBODIMENTS

Further alternatives and embodiments of his invention as describedbelow.

In other embodiments, the extent and use of the VPBRT can be reducedwithin the CCGE (e.g., between the VDMMD and the VOGB where the use of apacket based radio transport protocol may be negated if/when the CCDSNis sufficient to ensure connectivity via a regular IP network thatdelivers a specified digitized RF integrity. Or additionally, where theVRBRT and the VDMMD VMs and instances reside on the same physical and/orlocalized computational hardware), and where the VRBRT and the VOGB VMsand instances reside on the same physical and/or localized computationalhardware)

In other embodiments, the use of digitized and/or analog upconvertersand downconverters are permitted in the satellite communication system(e.g., the TRDS may use an upconverter to convert intermediate frequency(IF) to desired radio frequency (RF), and the RRFDS may use adownconverter to convert from desired RF to IF). In such embodiments,the digitized signals are manipulated in IF (or another frequency) andtransported by means of the VPBRT and the OBPPBRT.

In other embodiments, the GOCFLS is permitted to employ an analog systemto carry the transmit and receive antenna element signals between theCCGE and the satellite. In such an embodiment the transmit ISs receivedfrom the VPBRT are converted to analog RF signals via collocateddigital-to-analog converter hardware incorporating an RTP and networkconnection to the CCDSN, and then modulated over multimode free spaceoptical wavelengths for transmission to the satellite via the GOFLS.Additionally, analog RAE signals are received from the satellite overmultimode free space optical wavelengths and then converted to digitizedRF signals and ISs via collocated analog-to-digital converter hardwareincorporating an RTP and network connection to the CCDSN, and thenpassed to the VOGB. This is not the preferred embodiment and is detailedto show the versatility of the virtualized components of the satellitecommunications system, if an analog GOCFLS was desired or specified. Afully analog system onboard the satellite with muxing/demuxingfunctionality between the SOCFLS and the TRDS and the RRFDS ispermitted. Each TAE and RAE signal is transferred to and from thesatellite in analog IF or RF and is carried between the GOCFLS and theSOCFLS with analog modulation of the IF or RF signals over opticalcarrier waves.

In other embodiments, the use of multiple radio frequency (RF) feederlink systems is permitted with a single or plurality of concurrentoperational CCGEs supporting a single satellite.

In other embodiments, the TRFDS, OBPDAC, the RRFDS, OBPADC and theantenna system configuration can be designed to utilize components, suchas but not limited to, direct microwave digitization hardware capable ofinput and output of RF from baseband to Ka band (and higher) and/ortunable ultra-wideband (UWB) MMIC hardware (e.g., power amplifiers, lownoise amplifiers, bandpass filters etc.) capable of input and output ofRF from baseband to Ka band (and higher). In some embodiments, theCCGMIS can orchestrate a dynamic multi air interface operation where asingle or plurality of VSLAISs can change from one RF spectrum band(e.g., L-band) with a specific configuration of STs, to another singleor plurality of VSLAISs with a different RF spectrum band (e.g.,Ka-band) with another specific configuration of STs, through virtualizedresource reconfiguration. Such an embodiment would allow one specific RFspectrum band to operate from the satellite at any instance, however theCCGMIS would permit switching between RF spectrum bands and STconfigurations on a frequent (even sub-second) basis. Furtherembodiments, utilizing future hardware componentry on the satellitewould permit the end-to-end satellite communication system and theCCGMIS to allow multi RF spectrum band and multi ST configurations tooperate concurrently on the satellite.

In other embodiments, the use of an automatic and dynamicreconfiguration system is employed within the CCGMIS. Traditionalgateway implementations today rely on extensive, bespoke and cumbersomephysical RF distribution systems and infrastructure (e.g., waveguide,analog modems, upconverters, downconverters, amplifiers, filters etc.),and is commonly referred to as RF stove piping. Inflexibility anddifficulty in reconfiguration are amongst the many drawbacks withtraditional gateway implementations. As, the satellite communicationsystem relies on a fully cloud computing virtualized gatewayinfrastructure, all functions are established with multiple VMs,instances, and/or other cloud computing resources supporting thedifferent functions within the CCGE. The use of digitized RF signals anda packet based radio transport protocol between the CCGE and thesatellite or plurality of satellites ensures that no physical RFdistribution and bespoke infrastructure deployments are required withinthe CCGE. In effect, the CCGE creates a software defined gateway system,as it is physically independent of any specific piece of computationalhardware and/or analog RF hardware componentry. The CCGE enables fullnetwork agility, across the full view of the satellite, through thecloud computing infrastructure that in turn provides the re-provisioningor reconfiguration ability, with the adding, subtracting or expanding oftechnological computational resources. The CCGE therefore allows thereconfiguration of the network architecture across the entire (orpartial) resource of the satellite or fleet of satellites. The CCGMIScan reconfigure all or a sub-set of the sub-systems and/or theirparameters in the cloud computing virtual environment. For example, theCCGMIS can reconfigure the whole (or a single or plurality of partialsections) of the satellite communications system, utilizing multipleVSLAIS in multiple combinations and configurations, with multiple userdata signals combinations and configurations, with multiple combinationsof air interface types, within multiple user spot beam combinations andconfigurations, therefore supporting multiple combinations andconfigurations of STs. Such reconfigurations can be performed on aregular or irregular basis and even down to a sub-second basis. In someembodiments, the CCGMIS can be configured to reconfigure a single orplurality of CCGEs and associated VSLAISs on a predefined basis. Infurther embodiments, the CCGMIS can utilize real-time intelligence, suchas but not limited to, artificial intelligence (AI) and/or machinelearning (ML), that can analyze instantaneous loading across thesatellite communication system(s) and reconfigure the associated CCGEbased on AI/ML algorithms and operator defined parameters and metrics,in a dynamic environment. In such embodiments, the CCGE providesunlimited satellite communication system (and its network topology)flexibility via the instantaneous reconfiguration of the cloud computingresource with multiple VMs and instances options. The CCGMIS caneffectively create completely disparate communication networks as andwhen configured, under the specification of operator defined parametersand metrics. This adds a totally new dimension and functionality toproviding end-to-end connectivity over a satellite or fleet ofsatellites. This allows a single of plurality operators (of variouslevels and permissions) to reconfigure the entire or partial satellitecommunication system resource without the need for any physical hardwarechanges within the CCGE. The GOCFLS and associated satellite, althoughhardware based, are independent of the CCGE configuration and cansupport an unlimited number of CCGE configurations and options. Suchfunctionality provides a single or plurality of operators the ability tomaximize the total available resource and efficiency of the satellitecommunication system, even allowing for the over-subscription of theentire or partial resource of the satellite or fleet of satellites.

In other embodiments, the implementation of a real time dynamiccoordination manager is employed within the CCGMIS. As the CCGE operateson a cloud computing virtualized infrastructure, it is thereforepossible for a single or plurality of CCGMISs to have a complete view ofa single or a plurality of satellites (fleet of satellites). Theassociated CCGIMS have full visibility of every operating configurationat every instant across the satellite or fleet of satellites. This isunlike traditional satellite communications that has an inherent highlyfragmented physical gateway networking and RF infrastructure, in whichthere is no ability to have any real-time detailed oversight across asingle satellite let alone a fleet of satellites. Coordinationagreements between varying fleet operators have been relatively simpleto implement with widebeam (non-spot beam) satellites. With HTS, VHTS,VVHTS and UHTS this has/will prove to be far more challenging, and nearimpossible, particularly with flexible satellite communication systemsincorporating traditional gateway implementations and utilizing dynamicbeamforming. The CCGIMS knows what capacity (spectrum and power) isbeing transmitted and received to/from each of the user spot beams atany point in time and knows the user spot beams' specificconfigurations. The CCGIMS can then automatically manage all real-timecoordination between adjacent satellites operated by the same fleetoperator. In other embodiments, where there is a plurality of fleetoperators, each operator's CCGIMS are configured to communicate witheach other and mange real-time coordination activities. In furtherembodiments an independent or master CCGIMS is employed to manage allreal-time coordination activities. The CCGIMS can map coordinationagreements between varying fleet operators and then ensure that anyand/or all instantaneous configurations are compliant and adhere to theagreements without any manual intervention. In other embodiments, theindependent or master CCGIMS can function as an intermediary allowingone fleet operator to forgo its higher level of priority on itssatellite to another fleet operator's satellite. This would incorporatea prior arrangement between the two respective fleet operators allowingthe fleet operator operating under a lower priority basis to transmit athigher power levels on its satellite when it is determined by the CCGIMSas to not cause disruption to the higher priority fleet operator'sadjacent satellite.

In other embodiments, an automatic tracking, identification, andmitigation of RF interference system can be incorporated into theCCGMIS. This function will allow the CCGMIS to provide real-timemonitoring, management, and rectification of RF interference from faultyor rogue STs (or other sources) and/or the identification and/orrectification of deliberate and malicious jamming of the RF signalsbetween the STs and the satellite. The CCGMIS coordinates the VDMMDand/or the (OBPADC and/or OBPDAC systems for digital signal processingtechniques to carry out such tasks, whilst the CCGIMS can utilizeintelligent software to determine interference and the source of it.Other embodiments where other sub-systems of the CCGE carry out thesecore functions is permitted.

From the foregoing, it can be seen that the present inventionaccomplishes at least all of the stated objectives.

LIST OF REFERENCE CHARACTERS

The following table of reference characters and descriptors are notexhaustive, nor limiting, and include reasonable equivalents. Ifpossible, elements identified by a reference character below and/orthose elements which are near ubiquitous within the art can replace orsupplement any element identified by another reference character.

TABLE 1 List of Reference Characters 100 communications platform 101cloud computing gateway ecosystem 102 first exemplary subscriberterminal 103 network 104d down link 104u uplink 105 first exemplary userspot beam 105d first exemplary downlink channel 105u first exemplaryuplink channel 106 second exemplary user spot beam 106d second exemplarydownlink channel 106u second exemplary uplink channel 107 thirdexemplary user spot beam 107d third exemplary downlink channel 107uthird exemplary uplink channel 108 second exemplary subscriber terminal109 third exemplary subscriber terminal 200 cloud computing gatewayecosystem (CCGE) 201 virtualized space link air interface system(VSLAIS) 202 networks 203 virtualized user data signal-spot beamcontroller (VUDSSBC) 204 virtualized digital modem, mapper and demapper(VDMMD) 205 first virtualized packet based radio transport (VPBRT) 206virtualized on-ground beamformer (VOGB) 207 ground opticalcommunications feeder link system (GOCFLS) 208 cloud computing gatewaymanagement and interface system (CCGMIS) 209 value-add products andservices 210 cloud connected digital switched network (CCDSN) 211 secondvirtualized packet based radio transport (VPBRT) 300 satellite 301 spaceoptical communication feeder link system (SOCFLS) 302 on-board digitalnetwork distribution system (OBDNDS) 303 on-board processor (OBP) 304on-board processor: packet based radio transport (OBPPBRT) 305 on-boardprocessor: digital-to-analog converters (OBPDAC) 306 on-board processor:analog-to-digital converters (OBPADC) 307 transmit RF distributionsystem (TRFDS) 308 receive RF distribution system (RRFDS) 309 transmitantenna element (TAE) 310 receive antenna elements (RAE) 400 low-latencyprivate global network infrastructure (PGNI)

Glossary

Unless defined otherwise, all technical and scientific terms used abovehave the same meaning as commonly understood by one of ordinary skill inthe art to which embodiments of the present invention pertain.

The terms “a,” “an,” and “the” include both singular and pluralreferents.

The term “or” is synonymous with “and/or” and means any one member orcombination of members of a particular list.

The terms “invention” or “present invention” are not intended to referto any single embodiment of the particular invention but encompass allpossible embodiments as described in the specification and the claims.

The term “about” as used herein refer to slight variations in numericalquantities with respect to any quantifiable variable. Inadvertent errorcan occur, for example, through use of typical measuring techniques orequipment or from differences in the manufacture, source, or purity ofcomponents.

The term “substantially” refers to a great or significant extent.“Substantially” can thus refer to a plurality, majority, and/or asupermajority of said quantifiable variable, given proper context.

The term “generally” encompasses both “about” and “substantially.”

The term “configured” describes structure capable of performing a taskor adopting a particular configuration. The term “configured” can beused interchangeably with other similar phrases, such as constructed,arranged, adapted, manufactured, and the like.

Terms characterizing sequential order, a position, and/or an orientationare not limiting and are only referenced according to the viewspresented.

In communications and computing, a computer readable medium is a mediumcapable of storing data in a format readable by a mechanical device. Theterm “non-transitory” is used herein to refer to computer readable media(“CRM”) that store data for short periods or in the presence of powersuch as a memory device.

One or more embodiments described herein can be implemented usingprogrammatic modules, engines, or components. A programmatic module,engine, or component can include a program, a sub-routine, a portion ofa program, or a software component or a hardware component capable ofperforming one or more stated tasks or functions. A module or componentcan exist on a hardware component independently of other modules orcomponents. Alternatively, a module or component can be a shared elementor process of other modules, programs, or machines.

A processing unit, also called a processor, is an electronic circuitwhich performs operations on some external data source, usually memoryor some other data stream. Non-limiting examples of processors include amicroprocessor, a microcontroller, an arithmetic logic unit (“ALU”), andmost notably, a central processing unit (“CPU”). A CPU, also called acentral processor or main processor, is the electronic circuitry withina computer that carries out the instructions of a computer program byperforming the basic arithmetic, logic, controlling, and input/output(“I/O”) operations specified by the instructions. Processing units arecommon in tablets, telephones, handheld devices, laptops, user displays,smart devices (TV, speaker, watch, etc.), and other computing devices.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service.

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

The “scope” of the present invention is defined by the appended claims,along with the full scope of equivalents to which such claims areentitled. The scope of the invention is further qualified as includingany possible modification to any of the aspects and/or embodimentsdisclosed herein which would result in other embodiments, combinations,subcombinations, or the like that would be obvious to those skilled inthe art.

What is claimed is:
 1. A method of wirelessly communicating using cloudcomputing virtualized gateways, radio transport protocol, and on-groundbeamforming comprising: communicatively coupling at least one cloudcomputing gateway ecosystem (CCGE) to a plurality of subscriberterminals; illuminating specific regions of the Earth's surface withforward link user spot beams that include the subscriber terminals,wherein each forward link user spot beam includes a downlink channel;allowing forward communication between the CCGE and the communicationsplatform over a forward link; creating data signals for the forward linkbased upon received data; outputting the forward link user data signalsto a controller configured to package the data signals together and mapthe forward link user data signals to an associated forward link userspot beam; creating digitized RF carrier waves in a particular RF; anddigitally modulating and mapping bit streams that are beamformed andtransported within packet-based radio transport to a ground opticalcommunication feeder link system (GOCFLS) located within a field of viewof the communications platform.
 2. The method of claim 1, furthercomprising monitoring and controlling a feeder link resiliency systemthat allows for switching of CCGEs and associated GOCFLSs to ensureoperator specified availability of the feeder link system to thecommunications platform.
 3. The method of claim 1, wherein thesubscriber terminals are selected from the group consisting of: awireless modem, a cellular telephone, a wireless handset, a datatransceiver, a paging or positioning determination receiver, a mobileradio-telephone, and a head end of a local network.
 4. The method ofclaim 1, wherein the communications platform includes a plurality ofsub-systems selected from the group consisting of: a power source, solarpanels, a propulsion system, a momentum control system, and an attitudecontrol system.
 5. The method of claim 4, wherein the plurality ofsubsystems utilize core cloud computing resources that are provided at acloud-computing data center (CDC) comprising one or more componentsselected form the group consisting of: a computer, a server, a database,a network, an analytics based software application, a control system,intelligence capabilities, and on-demand web-based services.
 6. Themethod of claim 1, further comprising: delivering the CCGE via a publiccloud, private cloud, or hybrid cloud on-premises solution.
 7. Themethod of claim 1, wherein the forward link is associated with acorresponding return link.
 8. The method of claim 1, further comprising:sensing, monitoring, and/or controlling environmental aspects of thecommunications platform; and managing and/or coordinating at least apartial amount of resources of the communications platform based uponthe sensed, monitored, and/or controlled environmental aspects.
 9. Themethod of claim 1, further comprising: transmitting and receivingmetadata selected from the group consisting of: bandwidth, signalsampling and resolution rates, I/Q values, amplification, conditioning,frequency, symbol rate, carrier spacing, roll-off factor, constantcoding and modulation (CCM), and adaptive coding and modulation (ACM)details.
 10. The method of claim 1, further comprising: storing softwareimages, run-time data, other non-RAM functional data, and/or OSI layerdata related to any one of all seven OSI layers.
 11. A digitized groundbased subsystem for use in transmitting an optical feeder uplink beam toa communications platform, the ground based subsystem comprising: amultiple element antenna array configured to receive the optical feederuplink beam and to use the multiple element antenna feed array toproduce and transmit a plurality of RF service downlink beams to aservice terminal; a cloud-computing data center (CDC); a virtualized airinterface system configured to accept a plurality of data streams,multiplex the data streams, and produce a plurality of user datasignals; a virtualized user data signal-spot beam controller (VUDSSBC)configured to accept the user data signals from the virtualized airinterface systems and combine subsets of the user data signals into aplurality of user spot beam signals; a virtualized digital modulator andmapper configured to accept the user spot beam signals from the VUDSSBCand convert each to a digitized RF user spot beam signal; a virtualizedon-ground beamformer (VOGB) configured to accept the digitized RF userspot beam signals from the virtualized digital modulator and mapper,produce or otherwise obtain phase and amplitude coefficients, and outputa plurality of digitized RF transmit antenna element signals independance of the plurality of the digitized RF user spot beam signalsand phase and amplitude beamforming coefficients; a virtualized packetbased radio transport (VPBRT) configured to accept the digitized RFtransmit antenna element signals from the VOGB and packetizes in aplurality of information streams for multiplexing and transmission overa digital packet switched network; and a ground optical communicationsfeeder link system (GOCFLS) configured to accept the digitized RFtransmit antenna element signals in packetized form from the VPBRT andtransmit the RF transmit antenna element signals to the communicationsplatform.
 12. The subsystem of claim 11, further comprising: a cloudcomputing gateway management and interface system (CCGMIS) configured tomonitor the GOCFLSs performance and dynamically orchestrate the groundbase subsystem, and the switching operations of the ground basesubsystem between different CDCs and GOCFLSs supporting thecommunications platforms.
 13. The subsystem of claim 11, furthercomprising: a CCGMIS configured to orchestrate a scheduled and/ordynamic operation of a plurality of virtualized air interface systemsbetween active, dormant and/or modified states.
 14. The subsystem ofclaim 11, further comprising: a CCGMIS configured with a plurality ofcommunications platforms' inter-coordination agreement parameters tomonitor and control the user spot beam RF frequency and powercoordination across the plurality of the communications platforms.
 15. Asubsystem for a space based satellite comprising: a satellite bussystem; a space optical communication feeder link system (SOCFLS)configured to accept digitized RF transmit antenna element signals inpacketized form from a ground optical communications feeder link system(GOCFLS); an on-board digital network distribution system (OBDNDS)configured to accept the digitized RF transmit antenna element signalsfrom the SOCFLS and perform packet based switched networking functionsaboard the satellite; an on-board processor: packet based radiotransport (OBPPBRT) configured to accept the digitized RF transmitantenna element signals in packetized form from the OBDNDS thatde-multiplexes and de-packetizes information streams; a plurality ofon-board processor: digital-to-analog converters (OBPDAC) configured toaccept the de-packetized digitized RF transmit antenna element signalsfrom the OBPPBRT, and converting to a plurality of analog RF transmitantenna element signals; a transmit RF distribution system (TRFDS)configured to accept the analog RF transmit antenna element signals fromthe OBPDAC, and distribute through a plurality of analog RF chains; anda plurality of transmit antenna elements configured to accept a singleanalog RF transmit antenna element signal from the TRFDS to produce andtransmit a plurality of RF service downlink beams to service terminals.16. The subsystem of claim 15, further comprising: a cloud computinggateway management and interface system (CCGMIS) configured to monitorthe GOCFLS's performance and dynamically orchestrate a ground basedsubsystem, and the switching operations of the ground base subsystembetween different cloud-computing data centers (CDCs) and GOCFLSssupporting a single or plurality of satellites.
 17. The subsystem ofclaim 15, further comprising: a CCGMIS configured to orchestrate ascheduled and/or dynamic operation of a plurality of virtualized spacelink air interface system (VSLAIS) between active, dormant and/ormodified states.
 18. The subsystem of claim 15, further comprising: aCCGMIS configured with a plurality of satellites' inter-coordinationagreement parameters to monitor and control a user spot beam RFfrequency and power coordination across the plurality of the satellites.19. The subsystem of claim 15, wherein said satellite furthercomprising: an OBPDAC configured to support operation across multiple RFspectrum bands; a TRFDS configured to support operation across multipleRF spectrum bands; a plurality of transmit antenna elements configuredto support operation across multiple RF spectrum bands; and an antennaconfigured to support operation across multiple RF spectrum bands. 20.The subsystem of claim 19, further comprising: a CCGMIS configured toorchestrate a scheduled and/or dynamic operation of a plurality ofVSLAISs of various RF spectrum bands between active, dormant and/ormodified states.